[JENKINS-45924] issues in passing node parameter plugin in pipeline

In pipeline it has to execute on multiple nodes parallel based on selection of node parameter possible nodes option.

Used org.jvnet.jenkins.plugins.nodelabelparameter.NodeParameterValue('UPSTREAM_NODE', '', 'EQA') it is executing only on one node, it should execute on all nodes defined in label.

 

Based on the selection it should execute on all the selected nodes from the above picture.

 

---
Originally reported by rmahesh, imported from: issues in passing node parameter plugin in pipeline

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

Raw content of original issue

In pipeline it has to execute on multiple nodes parallel based on selection of node parameter possible nodes option.


Used org.jvnet.jenkins.plugins.nodelabelparameter.NodeParameterValue('UPSTREAM_NODE', '', 'EQA') it is executing only on one node, it should execute on all nodes defined in label.




 


Based on the selection it should execute on all the selected nodes from the above picture.


 

1 attachment

- [image-2017-08-02-12-26-18-520.png](https://issues.jenkins.io/secure/attachment/39119/image-2017-08-02-12-26-18-520.png)
> 

Start by reproducing the pipeline behavior with org.jvnet.jenkins.plugins.nodelabelparameter.NodeParameterValue using the UPSTREAM_NODE parameter and EQA label. Trace how the nodelabelparameter-plugin handles selected nodes; done means the pipeline executes in parallel on all nodes defined by the selected label rather than only one.

Written by the indexing model from the issue text.