[JENKINS-32939] When triggered by timer, Job with "NodeLabel Parameter Plugin" does not build in parallel on all nodes which share a label.

Hello,

I set up a job which is supposed to be build on all slave nodes sharing a label. I try to achieve this using the NodeLabel Parameter Plugin version 1.7.1.

I selected "Run on all nodes matching the label", and "Run regardless of result".

However, when I trigger the job by hand, it runs on all nodes matching the label. By when started by timmer, it only runs on a random node. The one node changes between iterations.

I include screenshots of my setup as attachments. Jenkins version is 1.643.

---
Originally reported by liangbo, imported from: When triggered by timer, Job with "NodeLabel Parameter Plugin" does not build in parallel on all nodes which share a label.

• assignee: escoem
  
• status: Open
  
• priority: Major
  
• component(s): nodelabelparameter-plugin
  
• label(s): nodelabelparameter
  
• resolution: Unresolved
  
• votes: 3
  
• watchers: 6
  
• imported: 20251210-235911
  

Raw content of original issue

Hello,


I set up a job which is supposed to be build on all slave nodes sharing a label. I try to achieve this using the NodeLabel Parameter Plugin version 1.7.1. 

I selected "Run on all nodes matching the label", and "Run regardless of result".


However, when I trigger the job by hand, it runs on all nodes matching the label. By when started by timmer, it only runs on a random node. The one node changes between iterations.


I include screenshots of my setup as attachments. Jenkins version is 1.643.

1 attachment

- [jenkins.png](https://issues.jenkins.io/secure/attachment/31852/jenkins.png)
> 

Start by reproducing the NodeLabel Parameter Plugin behavior with a timer-triggered job and the “Run on all nodes matching the label” setting on Jenkins 1.643. Compare it with the manual-trigger path and trace the plugin’s timer-related execution entry point. Done means timer-triggered builds run in parallel on every node sharing the selected label.

Written by the indexing model from the issue text.