Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-31391

Environment variable EXECUTOR_NUMBER should be usable inside node{} block

      Among few other environment variables that are generally available in freestyle job, EXECUTOR_NUMBER is not exposed in workflows.

      Referencing to the discussion in the attached URL, I would like to see this environment variable exposed especially inside node{} blocks where it makes the most sense. We have a similar use case as described in the discussion where workspaces are allocated based on the executor number, and currently workflow cannot handle this situation.

          [JENKINS-31391] Environment variable EXECUTOR_NUMBER should be usable inside node{} block

          Olli Sivonen created issue -
          Jesse Glick made changes -
          Link New: This issue is related to JENKINS-28131 [ JENKINS-28131 ]
          Jesse Glick made changes -
          Labels Original: environment-variables New: api environment-variables executor
          Jesse Glick made changes -
          Assignee Original: Jesse Glick [ jglick ] New: Luca Vitucci [ vexdev ]
          Jesse Glick made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Jesse Glick made changes -
          Remote Link New: This issue links to "PR 246 (Web Link)" [ 13526 ]
          Jesse Glick made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 166731 ] New: JNJira + In-Review [ 198037 ]
          Andrew Bayer made changes -
          Component/s New: pipeline-general [ 21692 ]
          Andrew Bayer made changes -
          Component/s Original: workflow-plugin [ 18820 ]

            vexdev Luca Vitucci
            oltzu Olli Sivonen
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: