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

Input steps to set their result as an environment variable

XMLWordPrintable

      The most idiomatic way to use input result values in pipeline model script is to set it as an (environment) variable which subsequent steps or stages can use.

      Pipeline model doesn't have explicit variables, so this is likely the only way.

          [JENKINS-38332] Input steps to set their result as an environment variable

          Patrick Wolf added a comment -

          This is a problem in both Declarative Pipeline and Pipeline Script. We need to solve the underlying problem for both

          Patrick Wolf added a comment - This is a problem in both Declarative Pipeline and Pipeline Script. We need to solve the underlying problem for both

          Andrew Bayer added a comment -

          Which means solving it in the input step, since we'll get whatever benefits from that for free elsewhere.

          Andrew Bayer added a comment - Which means solving it in the input step, since we'll get whatever benefits from that for free elsewhere.

          Andrew Bayer added a comment -

          Switching this over to JENKINS-38394 which is a more general-purpose version of this.

          Andrew Bayer added a comment - Switching this over to JENKINS-38394 which is a more general-purpose version of this.

          Michael Neale added a comment -

          hrmpw abayer don't you think this is worth solving for both?

          Michael Neale added a comment - hrmpw abayer don't you think this is worth solving for both?

          Liam Newman added a comment -

          Bulk closing resolved issues.

          Liam Newman added a comment - Bulk closing resolved issues.

            abayer Andrew Bayer
            michaelneale Michael Neale
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: