Details
-
Type:
Bug
-
Status: Resolved
-
Priority:
Critical
-
Resolution: Fixed
-
Component/s: throttle-concurrent-builds-plugin
-
Labels:None
-
Environment:Jenkins ver. 1.397
Plugin ver. 1.3
Description
I have two builds, A and B, which are each using "Restrict where this project can be run" on separate labels that identify exactly 1 slave machine each (one executor on each).
After the jobs were created and running, I created this category:
On Jenkins configure system:
Category Name: cat
Maximum Total Concurrent Builds: 1
Maximum Concurrent Builds Per Node: 0
On both Job configuration page:
Throttle Concurrent Build is checked
Maximum Total Concurrent Builds: 0
Maximum Concurrent Builds Per Node: 0
Multi-Project Throttle Category: cat is checked
Error case:
Click job A build now (wait to see that it has started), job B build now, job A build now. This results in A running with B waiting on the machine A uses (even though B is actually restricted to a different machine). Once A completes, B AND the second run of A both start running.
Most likely resolved by 1.4: Fixed problem with categories not checking for projects in pending state.
Will reopen if problem persists.