# Append a stage for every pipeline start

**URL:** <https://community.jenkins.io/t/append-a-stage-for-every-pipeline-start/16062>\
**Category:** Using Jenkins\
**Tags:** question, pipeline\
**Created:** [June 17, 2024, 8:34pm UTC](https://community.jenkins.io/t/append-a-stage-for-every-pipeline-start/16062 "2024-06-17T20:34:57Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![sodul](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/sodul/32/7828_2.png) [@sodul](https://community.jenkins.io/u/sodul)\
**Post date:** [June 17, 2024, 8:54pm UTC](https://community.jenkins.io/t/append-a-stage-for-every-pipeline-start/16062/2 "2024-06-17T20:54:50Z")

</div>

I have been looking for something similar where a library call could be triggered unconditionally for every single pipeline in order to inject bootstrapping or validation logic. So far this seems to be near impossible without the creation of a custom plugin in Java. The best you might be able to do is to add a CI check on all your jenkinsfiles and grep to ensure that the call you require is included in all jenkinsfiles. This is far from being bullet proof, but can help capture most of this.

> [@Trigger a groovy call in a jenkins library on every pipeline start](https://community.jenkins.io/t/trigger-a-groovy-call-in-a-jenkins-library-on-every-pipeline-start/15447/4):
>
> Do you have access to the repo via http? Then you could use the [http\_request](https://plugins.jenkins.io/http_request/) plugin in combination with the readYaml step. That would at least avoid that you have to clone the repo just to read a single file. You would still need your prepare stage in each pipeline but the approach doesn’t require a workspace.

---

_[View the full topic](https://community.jenkins.io/t/append-a-stage-for-every-pipeline-start/16062)._