How to avoid upstream trigger build cascade

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

How to avoid upstream trigger build cascade

Matthias Schöpfer
Hi!

Sorry, I have a question. We have some (not crazy, but still) number of jobs, that have dependencies to other jobs. The final job has about 15-20 deps. All those dependencies may have dependencies among each other. I added those dependencies to the "upstream trigger". Now, when the first job runs, it triggers jobs, that depend on it, *and* the final job. When those finish, they trigger other jobs *and* the final job. This ends in a cascade, which leads to 6-8 rebuilds of the final job. I would not like to hardcode the chain into the project, since the dependencies for example may change or are also used in other projects. I have seen, that other people suffered the same problem. One Solution, it seems, is the BlockBuildJob Plugin. But how can I activate it from a Jenkinsfile (declarative pipeline)? I tried it through options, but it does not seem to support this field. Any help is appreciated, Java / groovy is not my strong suit, I am more the C++ guy ;-)

My other idea was to scan the Queue myself, but I have not seen where query the Queue properly. Or to have a Seed job, that scans all jenkins jobs and builds MultiJob Jobs from it via jobDSL, but I did not succeed here either.

Regards,

  Matthias

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/89da2046-a89a-4e91-a0d2-f70d0fe0f2c7o%40googlegroups.com.