Jenkins Pipeline Environment Variables
Internal
Overview
Jenkins Pipeline exposes environment variables via the global variable env
, which is available from anywhere in the Jenkinsfile.
The full environment variables accessible from within Jenkins Pipeline is documented at http://<jenkins-instance-url>/pipeline-syntax/globals#env.
Programming Model
Accessing Environment Variables
echo "Running ${env.BUILD_ID} on ${env.JENKINS_URL}"
Setting Environment Variables
Setting an environment variable within a Jenkins Pipeline is accomplished differently depending on whether declarative or scripted pipeline is used.
Declarative pipeline supports an environment
directive:
pipeline {
agent any
environment {
CC = 'clang'
}
stages {
stage('Example') {
environment {
DEBUG_FLAGS = '-g'
}
steps {
sh 'printenv'
}
}
}
}
Scripted pipeline must use the withEnv step.
Environment Variables
BUILD_ID
The current build ID, identical to BUILD_NUMBER.
BUILD_NUMBER
The current build number, such as "153". Same as BUILD_ID.
BUILD_TAG
Contains job name, branch name, build number:
jenkins-${JOB_NAME}-${BUILD_NUMBER}
BUILD_URL
The URL where the results of this build can be found. Example: http://<jenkins-instance-url>/jenkins/job/MyJobName/17/
EXECUTOR_NUMBER
The unique number that identifies the current executor among executors of the same machine performing this build. This is the number shown in the "build executor status", except that the number starts from 0, not 1.
JAVA_HOME
If your job is configured to use a specific JDK, this variable is set to the JAVA_HOME of the specified JDK. When this variable is set, PATH is also updated to include the bin subdirectory of JAVA_HOME
JENKINS_URL
Full URL of Jenkins, such as https://example.com:port/jenkins/. It is only available if Jenkins URL set in "System Configuration".
JOB_NAME
Name of the project of this build.
JOB_BASE_NAME
NODE_NAME
The name of the node the current build is running on. Set to 'master' for master node.
WORKSPACE
The absolute path of the workspace