-
New Feature
-
Resolution: Fixed
-
Minor
-
None
I think it would be useful to limit the maximum number of builds of the same job.
Otherwise it could happen easily that all your executors are blocked by one single job.
I think it would be useful to limit the maximum number of builds of the same job.
Otherwise it could happen easily that all your executors are blocked by one single job.
In addition to the original limit reques: total number of concurrent builds (the original request),
I would like to see an additional limit: total number of concurrent builds per slave.
This is to handle a specific requirement I have: for some of my jobs, I can run builds concurrently on different machines, but I cannot have builds running concurrently on the same machine.
At the moment, the way I achieve this is by only having one executor per slave, but that imposes a stronger restriction that I really need. Having a concurrent-per-machine limit would meet my requirements exactly.