jenkinsci / jenkinsci/nodelabelparameter-plugin
[JENKINS-31042] Not running the job on all slaves in Label parameter
- Dominant language
- Java
- Stars
- 28
- Forks
- 59
- Avg merge
- 1h 24m
- Merged PRs (30d)
- 3
Description
I have assigned 5 slaves with the same label name (EX: dev_sev). I want to run a job concurrently on all the 5 slaves using the label parameter. Within my job, I have created parameterized Label and set label value to (dev_sev). I have also selected the following options, "Run on all nodes matching the label", "Run regardless of result", Node eligibility: All nodes", and "Execute concurrent builds if necessary".
When I execute the build, the label shows up and I can see all the 5 slaves show nodes, but the job is running on one of the nodes only. How do I resolve this issue with label param? I don't want to use a node parameter.
---
Originally reported by ahmedp, imported from: Not running the job on all slaves in Label parameter
Raw content of original issue
I have assigned 5 slaves with the same label name (EX: dev_sev). I want to run a job concurrently on all the 5 slaves using the label parameter. Within my job, I have created parameterized Label and set label value to (dev_sev). I have also selected the following options, "Run on all nodes matching the label", "Run regardless of result", Node eligibility: All nodes", and "Execute concurrent builds if necessary".
When I execute the build, the label shows up and I can see all the 5 slaves show nodes, but the job is running on one of the nodes only. How do I resolve this issue with label param? I don't want to use a node parameter.
- environment:
Running 1.625.1 on LInux
Contributor guide
Research direction
Reproduce the issue using Jenkins 1.625.1, five agents sharing the dev_sev label, and the listed Label parameter options. Start by inspecting the nodelabelparameter-plugin behavior for running on all matching nodes; done means one build executes concurrently across all five matching agents.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100