[JENKINS-45005] wrong node chosen for downstream job if upstream job uses nodelabelparameter

Hi,

 

Issue: wrong node chosen for downstream job if upstream job uses nodelabelparameter.

 

Sample:

Main job "A" has "This project is parameterized" with "Label=allnodes".

Also main job "A" has a Build "Trigger/call builds on other projects" which triggers job "B" passing "Current build parameters".

Job "B" has "This project is parameterized" disabled and "Restrict where this project can be run = supernode".

 

Result:

Job A always executed on nodes with label "allnodes" -> OK.

Job B also executes on nodes with label "allnodes" -> WRONG.

IMHO, job B should respect "This project is parameterized" and be executed on "supernode" because it has disabled "This project is parameterized".

 

P.S. I am not sure which plugin is guilty here, while I suspect nodelabelparameter-plugin here, as we are just trying using it now and we are using parameterized-trigger-plugin for a years without any issues.

Thank you for the reply here!

 

 

---
Originally reported by taurus, imported from: wrong node chosen for downstream job if upstream job uses nodelabelparameter

• status: Open
  
• priority: Minor
  
• component(s): nodelabelparameter-plugin, parameterized-trigger-plugin
  
• label(s): nodelabelparameter, nodes, parameterized-trigger, plugin
  
• resolution: Unresolved
  
• votes: 5
  
• watchers: 4
  
• imported: 2025-12-07
  

Raw content of original issue

Hi,


 


Issue: wrong node chosen for downstream job if upstream job uses nodelabelparameter.


 


Sample:


Main job "A" has "This project is parameterized" with "Label=allnodes".


Also main job "A" has a Build "Trigger/call builds on other projects" which triggers job "B" passing "Current build parameters".


Job "B" has "This project is parameterized" disabled and "Restrict where this project can be run = supernode".


 


Result:


Job A always executed on nodes with label "allnodes" -> OK.


Job B also executes on nodes with label "allnodes" -> WRONG.


IMHO, job B should respect "This project is parameterized" and be executed on "supernode" because it has disabled "This project is parameterized".


 


P.S. I am not sure which plugin is guilty here, while I suspect nodelabelparameter-plugin here, as we are just trying using it now and we are using parameterized-trigger-plugin for a years without any issues.


Thank you for the reply here!


 


 

environment

```
jenkins: 2.46.3 LTS on Debian Jessie

nodelabelparameter-plugin: 1.7.2

parameterized-trigger: 2.33

java -version

openjdk version "1.8.0_131"

OpenJDK Runtime Environment (build 1.8.0_131-8u131-b11-1~bpo8+1-b11)

OpenJDK 64-Bit Server VM (build 25.131-b11, mixed mode)

```