-
Bug
-
Resolution: Unresolved
-
Critical
-
Jenkins 1.598
BuildableItems (Subtasks) are miscounted in the queue
Expected:
When a labeled job is in the queue its nodeprovisioner should report excess load and provision a new node. The "free roaming" nodeprovisioner should report no load and not provision a new node.
Actual:
In addition to JENKINS-25207 (The free roaming nodeprovisioner spawns nodes even though the job is labeled), it is possible for the appropriate nodeprovisioner to not report load because of use of == on the label.
Technical:
Labels are compared in a number of places with == instead of equals
Additionally af55e5345628d31f49390e11a473079bed750fd9, modified the behaviour of the "free roaming" label in the queue. This results in spawning nodes for "free roaming" jobs, even when none exist.
I have included a pull request that resolves these issues.
- is related to
-
JENKINS-25207 NodeProvisioner: multiple instances spawned if Cloud is not EXCLUSIVE
-
- Open
-
[JENKINS-27034] BuildableItems (Subtasks) are miscounted in the queue
Environment | New: Jenkins 1.598 |
Link | New: This issue is related to JENKINS-25207 [ JENKINS-25207 ] |
Priority | Original: Minor [ 4 ] | New: Major [ 3 ] |
Priority | Original: Major [ 3 ] | New: Critical [ 2 ] |
Workflow | Original: JNJira [ 161225 ] | New: JNJira + In-Review [ 180617 ] |
The pull request in this issue should resolve spawning non-exclusive nodes when only labeled jobs are in the queue.