-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Platform: All, OS: All
I'm running Hudson 1.252, with two build executors and Locks plugin 0.2
Situation: two or more jobs are enqueued and executor #1 is building, while the
#2 is idle since all jobs share the same lock label.
If I cancel the build on #1, two enqueued jobs start building at the same time,
using the two executors and ignoring the lock.
All jobs are free style.
This is an underlying bug in the core of hudson in how it manages the queue entries.
I'm going to add some workaround code.
The net effect of the workaround is that when this situation arises, all the
jobs will start executing, but the locks-and-latches plugin will delay each job
such that only one can pass the lock at any moment in time.
They'll look like they're all building, but in fact only one will be inside the lock