Environment vars with multiple substitutions are not set

XMLWordPrintable

    • Pipeline - July/August

      Attempting to use multiple substituted values in an environment property causes it to silently fail to be set.

      Example script

      pipeline {
    agent any
    stages {
        stage('Build') {
            environment {
                AAA_Key = "${EXECUTOR_NUMBER} ${BUILD_NUMBER}"
                AAA_BN_ONLY = "${BUILD_NUMBER}"
                AAA_EN_ONLY = "${EXECUTOR_NUMBER}"
            }
            steps {
                bat 'set'
            }
        }
    }
}

      Current output

      c:\w\Pipeline Experimental\default>set
AAA_BN_ONLY=36
AAA_EN_ONLY=1

      Current workaround is to use withEnv directly, which doesn't appear to suffer from this issue

            Assignee:
            Andrew Bayer
            Reporter:
            Philip Peitsch
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: