jenkinsci / jenkinsci/nodelabelparameter-plugin
[JENKINS-58833] NodeLabel Parameter Plugin does not work for concurrent
- Dominant language
- Java
- Stars
- 28
- Forks
- 59
- Avg merge
- 1h 24m
- Merged PRs (30d)
- 3
Description
I created a project to run on agents. The project causes the agent's workspace to be updated with the latest from Perforce (SCM software).
The project has:
- Allow multi node selection for concurrent builds configured
- Execute concurrent builds if necessary configured.
- Restrict whre this project can be run disabled.
Master has 8 executors, slaves have 1 executor
If I select master, node1 and node2 - only master runs.
All should run.
If I select node1 and node - node 1 runs, and once that finishes node2 runs.
node1 and node2 should run at the same time on the two agent nodes.
---
Originally reported by rocha_stratovan, imported from: NodeLabel Parameter Plugin does not work for concurrent
Raw content of original issue
I created a project to run on agents. The project causes the agent's workspace to be updated with the latest from Perforce (SCM software).
The project has:
- Allow multi node selection for concurrent builds configured
- Execute concurrent builds if necessary configured.
- Restrict whre this project can be run disabled.
Master has 8 executors, slaves have 1 executor
If I select master, node1 and node2 - only master runs.
All should run.
If I select node1 and node - node 1 runs, and once that finishes node2 runs.
node1 and node2 should run at the same time on the two agent nodes.
environment
```
Jenkins 2.176.2
Windows 10
Internet Explorer, Firefox, Chrome
Plugin version 1.72
```
Contributor guide
Research direction
Start by reproducing the reported configuration with the master, node1, and node2 using concurrent builds and the NodeLabel Parameter Plugin. Inspect the plugin's implementation and available tests for multi-node selection and executor scheduling. Done means all selected nodes run concurrently as expected, including two agent nodes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100