CODEWITHSUNDEEP
jenkinscontinuous-integration
Charlie Fish
Charlie Fish

Reputation: 20546

Jenkins Build Queue Limit

I've noticed that there seems to be a build queue limit of one in Jenkins. When I trigger a lot of builds it seems to only place a max of one build in the build queue. Is there a way to remove this limit so there can be more then one build in the build queue?

Upvotes: 3

Views: 12796

Answers (1)

Alex O
Alex O

Reputation: 8164

This is intended behaviour:

  • Normally, your jobs will depend on some input (from SCM, or from some upstream jobs)
  • If your slave capacity is too low to catch up with each and every build, then you'd normally want to test/build/... only the very latest "item".

This is the default behaviour. Without that, there'd be a risk that the build queue grows indefinitely.

On top of that, Jenkins does not track the properties of normal build requests -- they all look the same, and Jenkins can not (for example) separate different SCM states that existed at different triggering times.

This is however exactly the point that gives you a workaround: parameterize your jobs, and then use for example the Trigger parameterized build on other projects post-build action to trigger those. Then Jenkins will queue each build request individually -- and inside your job, you can use the parameter to find out what exactly has to be done.

Jenkins will squash queued parameterized builds that have identical parameter values (thanks to user "atline" for checking).

Upvotes: 9

Related Questions