-
Bug
-
Resolution: Fixed
-
Minor
-
Jenkins 1.643 on Windows Server 2012R2 x64
Java 1.8.0_20 x86
Node and Label Parameter Plugin 1.7.1
-
-
1.11.0
I have multiple agents that have multiple labels\tags. Four of those agents are online and all 4 have 'sales' (no quotes) as one of their labels.
I add a label parameter to a job, and I specify 'sales' as the value (no quotes).
The job runs fine, and it targets all four agents. Unfortunately, it runs twice on the first agent (5 iterations total). If I use a NODE parameter instead, and select all 4 agents, it runs 4 times (once on each).
I have checked the box "Run on all nodes matching the label". I have selected "Run regardless of result" radio button. In terms of Node eligibility, I have selected "Ignore offline nodes".
It has nothing to do with that particular agent (agentA), because when I take it offline, and run the job again using the same label, the job is run twice on a different agent(agentB), and only once and the other two agents (agentC,agentD).
[JENKINS-33756] Job is run twice on first agent using label parameter
Rob Pimentel
created issue -
| Workflow | Original: JNJira [ 169731 ] | New: JNJira + In-Review [ 183629 ] |
Shivaji Pai
added a comment - This issues seems to be there in 2.60.2 as well.
Its a overload , we have a job that runs for 3 hours , the unwanted repeat is creating a overload
Shivaji Pai
added a comment - This issues seems to be there in 2.60.2 as well.
Its a overload , we have a job that runs for 3 hours , the unwanted repeat is creating a overload 
Sourish Banerjee
added a comment - I am facing the same problem.
Do we have a fix for this issue ? 
Benjamin Dewez
added a comment - We have the same issue on our Jenkins instance.
Jenkins: 2.73.1
Plugin: Node and Label Parameter Plugin 1.7.2
Redhat 7
Benjamin Dewez
added a comment - We have the same issue on our Jenkins instance.
Jenkins: 2.73.1
Plugin: Node and Label Parameter Plugin 1.7.2
Redhat 7 
Humphrey Lui
added a comment - Can you get the expected behavior after checking "Execute concurrent builds if necessary" ?
Humphrey Lui
added a comment - Can you get the expected behavior after checking "Execute concurrent builds if necessary" ? 
Jason Stanley
added a comment - Also hitting this problem on Jenkins ver. 2.121.2 plugin version 1.7.2
Red Hat 7
Jason Stanley
added a comment - Also hitting this problem on Jenkins ver. 2.121.2 plugin version 1.7.2
Red Hat 7 | Remote Link | New: This issue links to "Pull request 17 - do not run twice on first agent that matches the label (Web Link)" [ 27785 ] |
| Summary | Original: Job is run twice on first slave using label parameter | New: Job is run twice on first agent using label parameter |
I hit this today, it's because of computeNextLabels() doesn't remove instances of 'label' from 'nextLabels' when looking for matches and populating it in the @DataBoundConstructor in the LabelParameterValue class
So the runs are as follows.
(NodeA) -> NodeA -> NodeB
Teardown
(NodeA) -> NodeB
Teardown
(NodeB)
I'm not sure if this should be a minor bug but rather major, as if it's a long or destructive job, it would more than likely yield undesirable results.