Updating environment global variable in Jenkins pipeline from the stage level - is it possible?

You can't override the environment variable defined in the environment {} block. However, there is one trick you might want to use. You can refer to ACC environment variable in two ways:

• explicitly by env.ACC
• implicitly by ACC

The value of env.ACC cannot be changed once set inside environment {} block, but ACC behaves in the following way: when the variable ACC is not set then the value of env.ACC gets accessed (if exists of course). But when ACC variable gets initialized in any stage, ACC refers to this newly set value in any stage. Consider the following example:

pipeline {    agent any    environment {        FOO = "initial FOO env value"    }    stages {        stage("Stage 1") {            steps {                script {                    echo "FOO is '${FOO}'" // prints: FOO is 'initial FOO env value'                    env.BAR = "bar"                }            }        }        stage("Stage 2") {            steps {                echo "env.BAR is '${BAR}'" // prints: env.BAR is 'bar'                echo "FOO is '${FOO}'" // prints: FOO is 'initial FOO env value'                echo "env.FOO is '${env.FOO}'" // prints: env.FOO is 'initial FOO env value'                script {                    FOO = "test2"                    env.BAR = "bar2"                }            }        }        stage("Stage 3") {            steps {                echo "FOO is '${FOO}'" // prints: FOO is 'test2'                echo "env.FOO is '${env.FOO}'" // prints: env.FOO is 'initial FOO env value'                echo "env.BAR is '${BAR}'" // prints: env.BAR is 'bar2'                script {                    FOO = "test3"                }                echo "FOO is '${FOO}'" // prints: FOO is 'test3'            }        }    }}

And as you can see in the above example, the only exception to the rule is if the environment variable gets initialized outside the environment {} block. For instance, env.BAR in this example was initialized in Stage 1, but the value of env.BAR could be changed in Stage 2 and Stage 3 sees changed value.

UPDATE 2019-12-18

There is one way to override the environment variable defined in the environment {} block - you can use withEnv() block that will allow you to override the existing env variable. It won't change the value of the environment defined, but it will override it inside the withEnv() block. Take a look at the following example:

pipeline {  agent any   stages {    stage("Test") {      environment {        FOO = "bar"      }      steps {        script {          withEnv(["FOO=newbar"]) {            echo "FOO = ${env.FOO}" // prints: FOO = newbar          }        }      }    }  }}

I also encourage you to check my "Jenkins Pipeline Environment Variables explained " video.

loggedInUser = ""node ("cm-windows") {withEnv(["UserLoggedIn='Vrishali'"]) {  echo env.UserLoggedIn          stage('Setup'){    def buildCause = currentBuild.getBuildCauses()[0]    def buildPrincipal = [type:"unknown", name:""]    def buildUserCause =     currentBuild.getRawBuild().getCause(hudson.model.Cause.UserIdCause)    buildPrincipal = [type:"user", name:buildCause.userId]    print "Prining.."    print buildCause.userId    print "Checking the env var"    print env.UserLoggedIn    echo "[*] Starting build (id: ${env.UserLoggedIn}) on ${env.UserLoggedIn}"      loggedInUser = buildCause.userId    echo "Loggedin user"    print loggedInUser    echo loggedInUser   } }stage ('override env'){            withEnv(["UserLoggedIn=${loggedInUser}"]) {       echo "inside 2 stgae"        echo loggedInUser        print loggedInUser         echo "env"        echo env.UserLoggedIn   }}

}