[JENKINS-45916] Path is not getting set correctly in pipeline when there is a variable present

Type: Bug
Resolution: Fixed
Priority: Minor
Component/s: pipeline-model-definition-plugin
Labels:
Environment:
Jenkins ver. 2.32.1
Pipeline 2.5
EnvInject 1.2

Similar Issues:
Powered by SuggestiMate

Show

After upgrading to latest Pipeline version and it's dependencies (we also upgraded the blue ocean plugins but don't think that caused an issue here), we noticed that the PATH was not getting set in our Jenkins Pipeline Jobs. After debugging found that if I set PATH to a string inside the "environment" section, as such:

environment

{ PATH="/a/new/bin:$PATH" }

The PATH was updated successfully without any issues. However if I introduce a variable, the path does not get updated, and defaults to what is on the agent that runs the job. Example:

pipeline

{ agent

{ label 'docker' }

    environment {
        PATH="/a/new/bin:${env.SCM_HOME}:$PATH"
        SCM_HOME="${env.SCM_HOME}"
   }
stages {
    stage ('build') {
      steps

{ echo "PATH=$PATH" echo "SCM_HOME=$SCM_HOME" }

}
}
}

OUTPUT:

[Pipeline] {

[Pipeline] withEnv

[Pipeline] {

[Pipeline] stage

[Pipeline] { (build)

[Pipeline] echoPATH=/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/bin

[Pipeline] echoSCM_HOME=/usr/local/bin/scmtools/

[Pipeline] }

[Pipeline] // stage

[Pipeline] }

[Pipeline] // withEnv

[Pipeline] }

[Pipeline] // node

[Pipeline] End of PipelineFinished: SUCCESS

Notice that SCM_HOME resolves fine outside of PATH and that /a/new/bin was not added to the path. However if I drop the variable it will set PATH fine.

depends on

JENKINS-42753 Generate runtime model directly from AST model

Closed

James Murphy created issue - 2017-08-01 22:07

James Murphy made changes - 2017-08-01 22:09

Description

Original: After upgrading to latest Pipeline version and it's dependencies (we also upgraded the blue ocean plugins but don't think that caused an issue here), we noticed that the PATH was not getting set in our Jenkins Pipeline Jobs. After debugging found that if I set PATH to a string inside the "environment" section, as such:

    environment \{
        PATH="/a/new/bin:$PATH"
   }

The PATH was updated successfully without any issues. However if I introduce a variable, the path does not get updated, and defaults to what is on the agent that runs the job. Example:

pipeline \{
      agent \{ label 'docker'    }
    environment \{
        PATH="/a/new/bin:$\{env.SCM_HOME}:$PATH"
        SCM_HOME="$\{env.SCM_HOME}"
   }
stages \{
    stage ('build') \{
      steps \{
        echo "PATH=$PATH"
        echo "SCM_HOME=$SCM_HOME"
      }
    }
}
}

OUTPUT:

{color:#9a9999}[Pipeline] \{{color}{color:#9a9999}[Pipeline] withEnv{color}{color:#9a9999}[Pipeline] \{{color}{color:#9a9999}[Pipeline] stage{color}{color:#9a9999}[Pipeline] \{ (build){color}{color:#9a9999}[Pipeline] echo{color}PATH=/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/bin{color:#9a9999}[Pipeline] echo{color}SCM_HOME=/usr/local/bin/scmtools/{color:#9a9999}[Pipeline] }{color}{color:#9a9999}[Pipeline] // stage{color}{color:#9a9999}[Pipeline] }{color}{color:#9a9999}[Pipeline] // withEnv{color}{color:#9a9999}[Pipeline] }{color}{color:#9a9999}[Pipeline] // node{color}{color:#9a9999}[Pipeline] End of Pipeline{color}Finished: SUCCESS

Notice that SCM_HOME resolves fine outside of PATH and that /a/new/bin was not added to the path. However if I drop the variable it will set PATH fine.

New: After upgrading to latest Pipeline version and it's dependencies (we also upgraded the blue ocean plugins but don't think that caused an issue here), we noticed that the PATH was not getting set in our Jenkins Pipeline Jobs. After debugging found that if I set PATH to a string inside the "environment" section, as such:

    environment \{
         PATH="/a/new/bin:$PATH"
    }

The PATH was updated successfully without any issues. However if I introduce a variable, the path does not get updated, and defaults to what is on the agent that runs the job. Example:

pipeline \{
       agent \{ label 'docker'    }
     environment \{
         PATH="/a/new/bin:$\{env.SCM_HOME}:$PATH"
         SCM_HOME="$\{env.SCM_HOME}"
    }
   stages \{
     stage ('build') \{
       steps \{
         echo "PATH=$PATH"
         echo "SCM_HOME=$SCM_HOME"
       }
     }
   }
}

OUTPUT:

{color:#9a9999}[Pipeline] \{{color}{color:#9a9999}[Pipeline] withEnv{color}

{color:#9a9999}[Pipeline] \{{color}{color:#9a9999}[Pipeline] stage{color}

{color:#9a9999}[Pipeline] \{ (build){color}

{color:#9a9999}[Pipeline] echo{color}PATH=/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/bin

{color:#9a9999}[Pipeline] echo{color}SCM_HOME=/usr/local/bin/scmtools/

{color:#9a9999}[Pipeline] }{color}{color:#9a9999}[Pipeline] // stage{color}

{color:#9a9999}[Pipeline] }{color}

{color:#9a9999}[Pipeline] // withEnv{color}{color:#9a9999}[Pipeline] }{color}

{color:#9a9999}[Pipeline] // node{color}

{color:#9a9999}[Pipeline] End of Pipeline{color}Finished: SUCCESS


Notice that SCM_HOME resolves fine outside of PATH and that /a/new/bin was not added to the path. However if I drop the variable it will set PATH fine.

James Murphy made changes - 2017-08-01 22:10

Description

Original: After upgrading to latest Pipeline version and it's dependencies (we also upgraded the blue ocean plugins but don't think that caused an issue here), we noticed that the PATH was not getting set in our Jenkins Pipeline Jobs. After debugging found that if I set PATH to a string inside the "environment" section, as such:

    environment \{
         PATH="/a/new/bin:$PATH"
    }

The PATH was updated successfully without any issues. However if I introduce a variable, the path does not get updated, and defaults to what is on the agent that runs the job. Example:

pipeline \{
       agent \{ label 'docker'    }
     environment \{
         PATH="/a/new/bin:$\{env.SCM_HOME}:$PATH"
         SCM_HOME="$\{env.SCM_HOME}"
    }
   stages \{
     stage ('build') \{
       steps \{
         echo "PATH=$PATH"
         echo "SCM_HOME=$SCM_HOME"
       }
     }
   }
}

OUTPUT:

{color:#9a9999}[Pipeline] \{{color}{color:#9a9999}[Pipeline] withEnv{color}

{color:#9a9999}[Pipeline] \{{color}{color:#9a9999}[Pipeline] stage{color}

{color:#9a9999}[Pipeline] \{ (build){color}

{color:#9a9999}[Pipeline] echo{color}PATH=/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/bin

{color:#9a9999}[Pipeline] echo{color}SCM_HOME=/usr/local/bin/scmtools/

{color:#9a9999}[Pipeline] }{color}{color:#9a9999}[Pipeline] // stage{color}

{color:#9a9999}[Pipeline] }{color}

{color:#9a9999}[Pipeline] // withEnv{color}{color:#9a9999}[Pipeline] }{color}

{color:#9a9999}[Pipeline] // node{color}

{color:#9a9999}[Pipeline] End of Pipeline{color}Finished: SUCCESS


Notice that SCM_HOME resolves fine outside of PATH and that /a/new/bin was not added to the path. However if I drop the variable it will set PATH fine.

New: After upgrading to latest Pipeline version and it's dependencies (we also upgraded the blue ocean plugins but don't think that caused an issue here), we noticed that the PATH was not getting set in our Jenkins Pipeline Jobs. After debugging found that if I set PATH to a string inside the "environment" section, as such:

    environment \{
         PATH="/a/new/bin:$PATH"
    }

The PATH was updated successfully without any issues. However if I introduce a variable, the path does not get updated, and defaults to what is on the agent that runs the job. Example:

pipeline \{
       agent \{ label 'docker'    }
     environment \{
         PATH="/a/new/bin:$\{env.SCM_HOME}:$PATH"
         SCM_HOME="$\{env.SCM_HOME}"
    }
   stages \{
     stage ('build') \{
       steps \{
         echo "PATH=$PATH"
         echo "SCM_HOME=$SCM_HOME"
       }
     }
   }
}

OUTPUT:

{color:#9a9999}[Pipeline] \{{color}

{color:#9a9999}[Pipeline] withEnv{color}

{color:#9a9999}[Pipeline] \{{color}

{color:#9a9999}[Pipeline] stage{color}

{color:#9a9999}[Pipeline] \{ (build){color}

{color:#9a9999}[Pipeline] echo{color}PATH=/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/bin

{color:#9a9999}[Pipeline] echo{color}SCM_HOME=/usr/local/bin/scmtools/

{color:#9a9999}[Pipeline] }{color}

{color:#9a9999}[Pipeline] // stage{color}

{color:#9a9999}[Pipeline] }{color}

{color:#9a9999}[Pipeline] // withEnv{color}

{color:#9a9999}[Pipeline] }{color}

{color:#9a9999}[Pipeline] // node{color}

{color:#9a9999}[Pipeline] End of Pipeline{color}Finished: SUCCESS


Notice that SCM_HOME resolves fine outside of PATH and that /a/new/bin was not added to the path. However if I drop the variable it will set PATH fine.

Andrew Bayer made changes - 2017-08-02 02:56

Component/s		New: pipeline-model-definition-plugin [ 21706 ]
Component/s	Original: pipeline [ 21692 ]
Assignee		New: Andrew Bayer [ abayer ]
Labels	Original: environment-variables jenkins pipeline	New: declarative-variable-and-method-resolution environment-variables jenkins pipeline

Andrew Bayer made changes - 2017-08-02 02:58

Status

Original: Open [ 1 ]

New: In Progress [ 3 ]

Andrew Bayer made changes - 2017-08-03 15:20

Link

New: This issue depends on ~~JENKINS-42753~~ [ ~~JENKINS-42753~~ ]

Andrew Bayer made changes - 2017-08-03 15:20

Resolution		New: Fixed [ 1 ]
Status	Original: In Progress [ 3 ]	New: Resolved [ 5 ]

Blanca Borro Escribano made changes - 2018-02-20 08:27

Resolution	Original: Fixed [ 1 ]
Status	Original: Resolved [ 5 ]	New: Reopened [ 4 ]

Andrew Bayer made changes - 2018-11-15 17:02

Resolution		New: Fixed [ 1 ]
Status	Original: Reopened [ 4 ]	New: Fixed but Unreleased [ 10203 ]

Daniel Sorensen made changes - 2019-11-08 15:31

Description

Original: After upgrading to latest Pipeline version and it's dependencies (we also upgraded the blue ocean plugins but don't think that caused an issue here), we noticed that the PATH was not getting set in our Jenkins Pipeline Jobs. After debugging found that if I set PATH to a string inside the "environment" section, as such:

    environment \{
         PATH="/a/new/bin:$PATH"
    }

The PATH was updated successfully without any issues. However if I introduce a variable, the path does not get updated, and defaults to what is on the agent that runs the job. Example:

pipeline \{
       agent \{ label 'docker'    }
     environment \{
         PATH="/a/new/bin:$\{env.SCM_HOME}:$PATH"
         SCM_HOME="$\{env.SCM_HOME}"
    }
   stages \{
     stage ('build') \{
       steps \{
         echo "PATH=$PATH"
         echo "SCM_HOME=$SCM_HOME"
       }
     }
   }
}

OUTPUT:

{color:#9a9999}[Pipeline] \{{color}

{color:#9a9999}[Pipeline] withEnv{color}

{color:#9a9999}[Pipeline] \{{color}

{color:#9a9999}[Pipeline] stage{color}

{color:#9a9999}[Pipeline] \{ (build){color}

{color:#9a9999}[Pipeline] echo{color}PATH=/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/bin

{color:#9a9999}[Pipeline] echo{color}SCM_HOME=/usr/local/bin/scmtools/

{color:#9a9999}[Pipeline] }{color}

{color:#9a9999}[Pipeline] // stage{color}

{color:#9a9999}[Pipeline] }{color}

{color:#9a9999}[Pipeline] // withEnv{color}

{color:#9a9999}[Pipeline] }{color}

{color:#9a9999}[Pipeline] // node{color}

{color:#9a9999}[Pipeline] End of Pipeline{color}Finished: SUCCESS


Notice that SCM_HOME resolves fine outside of PATH and that /a/new/bin was not added to the path. However if I drop the variable it will set PATH fine.

New: After upgrading to latest Pipeline version and it's dependencies (we also upgraded the blue ocean plugins but don't think that caused an issue here), we noticed that the PATH was not getting set in our Jenkins Pipeline Jobs. After debugging found that if I set PATH to a string inside the "environment" section, as such:

    environment {
         PATH="/a/new/bin:$PATH"
    }

The PATH was updated successfully without any issues. However if I introduce a variable, the path does not get updated, and defaults to what is on the agent that runs the job. Example:

pipeline {
       agent \{ label 'docker'    }
     environment {
         PATH="/a/new/bin:${env.SCM_HOME}:$PATH"
         SCM_HOME="${env.SCM_HOME}"
    }
   stages {
     stage ('build') {
       steps {
         echo "PATH=$PATH"
         echo "SCM_HOME=$SCM_HOME"
       }
     }
   }
}

OUTPUT:

{color:#9a9999}[Pipeline] {{color}

{color:#9a9999}[Pipeline] withEnv{color}

{color:#9a9999}[Pipeline] {{color}

{color:#9a9999}[Pipeline] stage{color}

{color:#9a9999}[Pipeline] { (build){color}

{color:#9a9999}[Pipeline] echo{color}PATH=/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/bin

{color:#9a9999}[Pipeline] echo{color}SCM_HOME=/usr/local/bin/scmtools/

{color:#9a9999}[Pipeline] }{color}

{color:#9a9999}[Pipeline] // stage{color}

{color:#9a9999}[Pipeline] }{color}

{color:#9a9999}[Pipeline] // withEnv{color}

{color:#9a9999}[Pipeline] }{color}

{color:#9a9999}[Pipeline] // node{color}

{color:#9a9999}[Pipeline] End of Pipeline{color}Finished: SUCCESS


Notice that SCM_HOME resolves fine outside of PATH and that /a/new/bin was not added to the path. However if I drop the variable it will set PATH fine.

Daniel Sorensen made changes - 2019-11-08 15:32

Description

Original: After upgrading to latest Pipeline version and it's dependencies (we also upgraded the blue ocean plugins but don't think that caused an issue here), we noticed that the PATH was not getting set in our Jenkins Pipeline Jobs. After debugging found that if I set PATH to a string inside the "environment" section, as such:

    environment {
         PATH="/a/new/bin:$PATH"
    }

The PATH was updated successfully without any issues. However if I introduce a variable, the path does not get updated, and defaults to what is on the agent that runs the job. Example:

pipeline {
       agent \{ label 'docker'    }
     environment {
         PATH="/a/new/bin:${env.SCM_HOME}:$PATH"
         SCM_HOME="${env.SCM_HOME}"
    }
   stages {
     stage ('build') {
       steps {
         echo "PATH=$PATH"
         echo "SCM_HOME=$SCM_HOME"
       }
     }
   }
}

OUTPUT:

{color:#9a9999}[Pipeline] {{color}

{color:#9a9999}[Pipeline] withEnv{color}

{color:#9a9999}[Pipeline] {{color}

{color:#9a9999}[Pipeline] stage{color}

{color:#9a9999}[Pipeline] { (build){color}

{color:#9a9999}[Pipeline] echo{color}PATH=/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/bin

{color:#9a9999}[Pipeline] echo{color}SCM_HOME=/usr/local/bin/scmtools/

{color:#9a9999}[Pipeline] }{color}

{color:#9a9999}[Pipeline] // stage{color}

{color:#9a9999}[Pipeline] }{color}

{color:#9a9999}[Pipeline] // withEnv{color}

{color:#9a9999}[Pipeline] }{color}

{color:#9a9999}[Pipeline] // node{color}

{color:#9a9999}[Pipeline] End of Pipeline{color}Finished: SUCCESS


Notice that SCM_HOME resolves fine outside of PATH and that /a/new/bin was not added to the path. However if I drop the variable it will set PATH fine.

New: After upgrading to latest Pipeline version and it's dependencies (we also upgraded the blue ocean plugins but don't think that caused an issue here), we noticed that the PATH was not getting set in our Jenkins Pipeline Jobs. After debugging found that if I set PATH to a string inside the "environment" section, as such:

    environment

{         PATH="/a/new/bin:$PATH"    }

The PATH was updated successfully without any issues. However if I introduce a variable, the path does not get updated, and defaults to what is on the agent that runs the job. Example:

pipeline

{       agent \\{ label 'docker'    }

    environment {
         PATH="/a/new/bin:${env.SCM_HOME}:$PATH"
         SCM_HOME="${env.SCM_HOME}"
    }
   stages {
     stage ('build') {
       steps

{         echo "PATH=$PATH"         echo "SCM_HOME=$SCM_HOME"       }

    }
   }
}

OUTPUT:

{color:#9a9999}[Pipeline] {{color}

{color:#9a9999}[Pipeline] withEnv{color}

{color:#9a9999}[Pipeline] {{color}

{color:#9a9999}[Pipeline] stage{color}

{color:#9a9999}[Pipeline] { (build){color}

{color:#9a9999}[Pipeline] echo{color}PATH=/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/bin

{color:#9a9999}[Pipeline] echo{color}SCM_HOME=/usr/local/bin/scmtools/

{color:#9a9999}[Pipeline] }{color}

{color:#9a9999}[Pipeline] // stage{color}

{color:#9a9999}[Pipeline] }{color}

{color:#9a9999}[Pipeline] // withEnv{color}

{color:#9a9999}[Pipeline] }{color}

{color:#9a9999}[Pipeline] // node{color}

{color:#9a9999}[Pipeline] End of Pipeline{color}Finished: SUCCESS


Notice that SCM_HOME resolves fine outside of PATH and that /a/new/bin was not added to the path. However if I drop the variable it will set PATH fine.

Assignee:: Andrew Bayer

Reporter:: James Murphy

Votes:: 0 Vote for this issue

Watchers:: 9 Start watching this issue

Created:: 2017-08-01 22:07

Updated:: 2021-04-28 14:13

Resolved:: 2018-11-15 17:02

Jenkins

Details

Description

Attachments

Issue Links

Activity

People

Dates