|
Description:
|
This is a problem because, if further builds are currently blocked (say, by being out of available executors), jenkins will quietly drop any additional attempts to queue a build - which seems at odds with the stated effect of allowing Jenkins to "schedule and execute multiple builds concurrently"
To replicate: Set available executors to one. Create a freestyle build; make it, say, printenv and sleep 30. Add a parameter and check "Execute concurrent builds if necessary" - it seems to me like this should allow unlimited parallel builds with different parameterized values; in practice, only two can exist - the one that's building right now, and one in the queue; attempting to start additional builds beyond that, even with different parameters, simply fails.
(My personal use case is a bit more complicated, with builds being blocked by things other than just insufficient available executors. But the underlying problem is the same.)
|
