The current build number, such as "153"
The current build id, such as "2005-08-22_23-59-59" (YYYY-MM-DD_hh-mm-ss, defunct since version 1.597)
The URL where the results of this build can be found (e.g.)
The name of the node the current build is running on. Equals 'master' for master node.
Name of the project of this build. This is the name you gave your job when you first set it up. It's the third column of the Jenkins Dashboard main page.
Set to the URL of the Jenkins master that's running the build. This value is used by Jenkins CLI for example
The unique number that identifies the current executor (among executors of the same machine) that's carrying out this build. This is the number you see in the "build executor status", except that the number starts from 0, not 1.
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 have $JAVA_HOME/bin.
The absolute path of the workspace.
For Subversion-based projects, this variable contains the revision number of the module. If you have more than one module specified, this won't be set.
For CVS-based projects, this variable contains the branch of the module. If CVS is configured to check out the trunk, this environment variable will not be set.
For Git-based projects, this variable contains the Git hash of the commit checked out for the build (like ce9a3c1404e8c91be604088670e93434c4253f03) (all the GIT_* variables require git plugin)
For Git-based projects, this variable contains the Git url (like email@example.com:user/repo.git or [https://github.com/user/repo.git)\\
For Git-based projects, this variable contains the Git branch that was checked out for the build (normally origin/master)