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

env.WHATEVER not considered for environment variable cross reference resolution in Declarative

    XMLWordPrintable

Details

    Description

      With an environment section like this:

      environment {
        FOO = "something"
        BAR = "${env.FOO} else"
      }

      The EnvVars-driven environment variable resolution/expansion doesn't know that env.FOO means that it needs to resolve FOO before resolving BAR, so there's no guarantee that'll actually happen in that order, and you may well get BAR as null else.

      Attachments

        Activity

          abayer Andrew Bayer created issue -
          abayer Andrew Bayer made changes -
          Field Original Value New Value
          Status Open [ 1 ] In Progress [ 3 ]
          abayer Andrew Bayer made changes -
          Resolution Fixed [ 1 ]
          Status In Progress [ 3 ] Resolved [ 5 ]
          bitwiseman Liam Newman made changes -
          Status Resolved [ 5 ] Closed [ 6 ]

          People

            abayer Andrew Bayer
            abayer Andrew Bayer
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: