Jenkins Tutorials: Jenkins Environment Variables in PowerShell

The following variables are available to PowerShell scripts

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)

Name of the project of this build, such as “foo”

String of “jenkins-${JOB_NAME}-${BUILD_NUMBER}”. Convenient to put into a resource file, a jar file, etc for easier identification.

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.

Name of the slave if the build is on a slave, or “master” if run on master

Whitespace-separated list of labels that the node is assigned.

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.

Full URL of Hudson, like http://server:port/hudson/

Full URL of Jenkins, like http://server:port/jenkins/

Full URL of this build, like http://server:port/jenkins/job/foo/15/

Full URL of this job, like http://server:port/jenkins/job/foo/

For Subversion-based projects, this variable contains the revision number of the module.

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.


Compress-Archive $env:WORKSPACE\\POCStudentCrud\\bin\\app.publish $env:WORKSPACE\\POCStudentCrud\\bin\\
Rajesh Kumar
Follow me
Notify of
1 Comment
Oldest Most Voted
Inline Feedbacks
View all comments
5 months ago

Useful post, thank you.

Would love your thoughts, please comment.x