[JENKINS-69820] Usage in jenkinsfiles

[jenkins-infra-bot]

I wish for an implementation of this plugin, that I can use in my Jenkinsfiles. Right now it's either not possible, or not straight forward, to configure a node/label parameter in the parameters-block of a Jenkinsfile.

If the functionality exists, extending the documenation would be appreciated.

I tried it this way:

parameters {
        $class: 'NodeParameterValue'(name: 'nodeName',labels: ['label1', 'label2'], nodeEligibility: [$class: 'IgnoreOfflineNodeEligibility'])
    } 

but Jenkins only accepts the "standard" classes for parameters.

---

Originally reported by ger_senshi, imported from: Usage in jenkinsfiles

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

Raw content of original issue

I wish for an implementation of this plugin, that I can use in my Jenkinsfiles. Right now it's either not possible, or not straight forward, to configure a node/label parameter in the parameters-block of a Jenkinsfile.

If the functionality exists, extending the documenation would be appreciated.

I tried it this way:

parameters {
        $class: 'NodeParameterValue'(name: 'nodeName',labels: ['label1', 'label2'], nodeEligibility: [$class: 'IgnoreOfflineNodeEligibility'])
    } 

but Jenkins only accepts the "standard" classes for parameters.

1 attachment

• image-2025-01-27-14-36-42-616.png

  

[jenkins-infra-bot]

markewaite:

• Original comment link
• Raw content of original comment:

  Good suggestion. Thanks for the request
  

Good suggestion. Thanks for the request

[jenkins-infra-bot]

giuliano:

• Original comment link
• Raw content of original comment:

  This is the exact "problem" I am encountering.
  
  
  Keeping all the configuration in the Jenkinsfile is so important for me that I thought the code-implementation of a parameter was a native way of setting a parameter when installing a parameter plugin.
  
  Therefore, I want to report this ticket to the developer team with an higher priority.
  

This is the exact "problem" I am encountering.

Keeping all the configuration in the Jenkinsfile is so important for me that I thought the code-implementation of a parameter was a native way of setting a parameter when installing a parameter plugin.

Therefore, I want to report this ticket to the developer team with an higher priority.

[jenkins-infra-bot]

giuliano:

• Original comment link
• Raw content of original comment:

  Obviously, I wish I could achieve it through the Dashboard -> <job_name> -> Pipeline Syntax -> Declarative Directive Generator's UI:
  
  
  

Obviously, I wish I could achieve it through the Dashboard -> -> Pipeline Syntax -> Declarative Directive Generator's UI:

[jenkins-infra-bot]

markewaite:

• Original comment link
• Raw content of original comment:

  Thanks for your comment giuliano.  I don't plan to work on this any time soon.  Other Jenkins activities are higher priority for me.  If you or someone else implements the changes, provides automated tests for the changes, and submits a pull request, I'm willing to review the pull request.
  

Thanks for your comment giuliano. I don't plan to work on this any time soon. Other Jenkins activities are higher priority for me. If you or someone else implements the changes, provides automated tests for the changes, and submits a pull request, I'm willing to review the pull request.