The following variables are available to PowerShell scripts
$ENV:BUILD_NUMBER
The current build number, such as “153”
$ENV:BUILD_ID
The current build id, such as “2005-08-22_23-59-59” (YYYY-MM-DD_hh-mm-ss)
$ENV:JOB_NAME
Name of the project of this build, such as “foo”
$ENV:BUILD_TAG
String of “jenkins-${JOB_NAME}-${BUILD_NUMBER}”. Convenient to put into a resource file, a jar file, etc for easier identification.
$ENV:EXECUTOR_NUMBER
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.
$ENV:NODE_NAME
Name of the slave if the build is on a slave, or “master” if run on master
$ENV:NODE_LABELS
Whitespace-separated list of labels that the node is assigned.
$ENV: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 have $JAVA_HOME/bin.
$ENV:WORKSPACE
The absolute path of the workspace.
$ENV:HUDSON_URL
Full URL of Hudson, like http://server:port/hudson/
$ENV:JENKINS_URL
Full URL of Jenkins, like http://server:port/jenkins/
$ENV:BUILD_URL
Full URL of this build, like http://server:port/jenkins/job/foo/15/
$ENV:JOB_URL
Full URL of this job, like http://server:port/jenkins/job/foo/
$ENV:SVN_REVISION
For Subversion-based projects, this variable contains the revision number of the module.
$ENV:CVS_BRANCH
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.
Example
Compress-Archive $env:WORKSPACE\\POCStudentCrud\\bin\\app.publish $env:WORKSPACE\\POCStudentCrud\\bin\\app.publish.zip
- Best AI tools for Software Engineers - November 4, 2024
- Installing Jupyter: Get up and running on your computer - November 2, 2024
- An Introduction of SymOps by SymOps.com - October 30, 2024
Useful post, thank you.