[JENKINS-47571] Pipeline Snippet Generator for 'build' steps doesn't generate proper code for node and label parameters

[jenkins-infra-bot]

Reporting this as suggested by jglick at https://stackoverflow.com/a/29806918/45375:

In short: job parameters of type "node" and "label" are not correctly instantiated by the Snippet Generator.

Current behavior:

When I use the Snippet Generator with "Build a job", the generated code is :

build job: 'test job', parameters: [<object of type org.jvnet.jenkins.plugins.nodelabelparameter.NodeParameterValue>]

Expected behavior (example, assuming a parameter name of "UPSTREAM_NODE", a node name of "my_node"):

build job: 'test job', parameters: [[$class: 'NodeParameterValue', name: 'UPSTREAM_NODE', labels: ['my_node'], nodeEligibility: [$class: 'AllNodeEligibility']]]

 

 

---

Originally reported by mklement0, imported from: Pipeline Snippet Generator for 'build' steps doesn't generate proper code for node and label parameters

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

Raw content of original issue

Reporting this as suggested by jglick at https://stackoverflow.com/a/29806918/45375:

In short: job parameters of type "node" and "label" are not correctly instantiated by the Snippet Generator.

Current behavior:


When I use the Snippet Generator with "Build a job", the generated code is :

build job: 'test job', parameters: [<object of type org.jvnet.jenkins.plugins.nodelabelparameter.NodeParameterValue>]




Expected behavior (example, assuming a parameter name of "UPSTREAM_NODE",  a node name of "my_node"):

build job: 'test job', parameters: [[$class: 'NodeParameterValue', name: 'UPSTREAM_NODE', labels: ['my_node'], nodeEligibility: [$class: 'AllNodeEligibility']]]


 
 

• environment: Jenkins v2.85, Node and Label parameter plugin v1.7.2

[jenkins-infra-bot]

davida2009:

• Original comment link
• Raw content of original comment:

  jglick I think this issue was filed in response to your answer to https://stackoverflow.com/questions/29794804/how-to-use-a-parameter-from-nodelabelparameter-plugin-with-the-build-step-of-j/29806918#29806918. I see a similar bug:
  
  <object of type org.jvnet.jenkins.plugins.nodelabelparameter.NodeParameterValue>,
  
  
  I see there's no resolution to this bug. Do you think it needs to be reallocated?
  

jglick I think this issue was filed in response to your answer to https://stackoverflow.com/questions/29794804/how-to-use-a-parameter-from-nodelabelparameter-plugin-with-the-build-step-of-j/29806918#29806918. I see a similar bug:

,

I see there's no resolution to this bug. Do you think it needs to be reallocated?

[jenkins-infra-bot]

jglick:

• Original comment link
• Raw content of original comment:

  If there is no resolution to the bug, either the maintainer of this plugin has not seen it, or does not have time to fix it, or there is no active maintainer at all. I have no idea.
  
  By the way, @Symbol has been available as a nicer alternative to $class for quite some time (perhaps this question predates it), so the desired snippet would be something more resembling
  
  
  build job: 'test job', parameters: [node(name: 'UPSTREAM_NODE', labels: 'my_node', eligibility: all())]
  
  
  

If there is no resolution to the bug, either the maintainer of this plugin has not seen it, or does not have time to fix it, or there is no active maintainer at all. I have no idea.

By the way, @​Symbol has been available as a nicer alternative to $class for quite some time (perhaps this question predates it), so the desired snippet would be something more resembling

build job: 'test job', parameters: [node(name: 'UPSTREAM_NODE', labels: 'my_node', eligibility: all())]

[jenkins-infra-bot]

davida2009:

• Original comment link
• Raw content of original comment:

  jglick Thanks for your reply and sorry to bother you.  I posted a related question on Stack Overflow. If you have time to have a look I would be very grateful.
  

jglick Thanks for your reply and sorry to bother you.  I posted a related question on Stack Overflow. If you have time to have a look I would be very grateful.