You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[JENKINS-76200] Fix label matching in itemsInQueueForThisSlave
Changed from checking only explicit node assignment (selfLabel) to using
Label.contains() which properly checks if a node can execute jobs based
on label matching. This fixes the issue where stopped instances would
only start for jobs explicitly tied to the node name, not for jobs that
match the node's labels.
Changes:
- Use assignedLabel.contains(selfNode) instead of assignedLabel == selfLabel
- Handle null assignedLabel (jobs that can run on any node)
- Added comment explaining the label matching logic
Now stopped instances will start for:
- Jobs with no label requirement (assignedLabel == null)
- Jobs whose labels match this node's capabilities (assignedLabel.contains(selfNode))
Before this fix, stopped instances only started for jobs explicitly tied to
the specific node name.
0 commit comments