In my setup each pipeline job running stashes lots of data. So if there are too many jobs running, the system will run out of disk space on some nodes or even the master.
Other motivation: in my pipelines some stages can only be run on a certain node. If the node becomes offline, jobs will all wait for the node to come online again. The jobs queue up in the build queue. As this might not be detected for a while, more and more jobs will queue up. It is likely that the master keeping the current stashes of all jobs running will run out of disk space eventually. So i would like to limit the number of jobs running to say 20. More precisely if 20 pipeline builds are running (not finished) currently, a new pipeline build A would not get executed but would stay in the build queue. If a pipeline build finishes, build A would be permitted to leave the build queue to be executed on a node. Tim -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/de644da3-d593-4494-8269-e0315832a37e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
