X

世界,您好!

The following variables are available to shell scriptsBRANCH_NAMEFor a multibranch project, this will be set to the name of the branch being built, for example in case you wish to deploy to production from master but not from feature branches; if corresponding to some kind of change request, the name is generally arbitrary (refer to CHANGE_ID and CHANGE_TARGET).CHANGE_IDFor a multibranch project corresponding to some kind of change request, this will be set to the change ID, such as a pull request number, if supported; else unset.CHANGE_URLFor a multibranch project corresponding to some kind of change request, this will be set to the change URL, if supported; else unset.CHANGE_TITLEFor a multibranch project corresponding to some kind of change request, this will be set to the title of the change, if supported; else unset.CHANGE_AUTHORFor a multibranch project corresponding to some kind of change request, this will be set to the username of the author of the proposed change, if supported; else unset.CHANGE_AUTHOR_DISPLAY_NAMEFor a multibranch project corresponding to some kind of change request, this will be set to the human name of the author, if supported; else unset.CHANGE_AUTHOR_EMAILFor a multibranch project corresponding to some kind of change request, this will be set to the email address of the author, if supported; else unset.CHANGE_TARGETFor a multibranch project corresponding to some kind of change request, this will be set to the target or base branch to which the change could be merged, if supported; else unset.BUILD_NUMBERThe current build number, such as “153”BUILD_IDThe current build ID, identical to BUILD_NUMBER for builds created in 1.597+, but a YYYY-MM-DD_hh-mm-ss timestamp for older buildsBUILD_DISPLAY_NAMEThe display name of the current build, which is something like “#153” by default.JOB_NAMEName of the project of this build, such as “foo” or “foo/bar”.JOB_BASE_NAMEShort Name of the project of this build stripping off folder paths, such as “foo” for “bar/foo”.BUILD_TAGString of “jenkins-${JOB_NAME}${BUILD_NUMBER}“. All forward slashes (“/”) in the JOB_NAME are replaced with dashes (“-“). Convenient to put into a resource file, a jar file, etc for easier identification.EXECUTOR_NUMBERThe 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.NODE_NAMEName of the agent if the build is on an agent, or “master” if run on masterNODE_LABELSWhitespace-separated list of labels that the node is assigned.WORKSPACEThe absolute path of the directory assigned to the build as a workspace.JENKINS_HOMEThe absolute path of the directory assigned on the master node for Jenkins to store data.JENKINS_URLFull URL of Jenkins, like http://server:port/jenkins/ (note: only available if Jenkins URL set in system configuration)BUILD_URLFull URL of this build, like http://server:port/jenkins/job/foo/15/ (Jenkins URL must be set)JOB_URLFull URL of this job, like http://server:port/jenkins/job/foo/ (Jenkins URL must be set)GIT_COMMITThe commit hash being checked out.GIT_PREVIOUS_COMMITThe hash of the commit last built on this branch, if any.GIT_PREVIOUS_SUCCESSFUL_COMMITThe hash of the commit last successfully built on this branch, if any.GIT_BRANCHThe remote branch name, if any.GIT_LOCAL_BRANCHThe local branch name being checked out, if applicable.GIT_URLThe remote URL. If there are multiple, will be GIT_URL_1GIT_URL_2, etc.GIT_COMMITTER_NAMEThe configured Git committer name, if any.GIT_AUTHOR_NAMEThe configured Git author name, if any.GIT_COMMITTER_EMAILThe configured Git committer email, if any.GIT_AUTHOR_EMAILThe configured Git author email, if any.SVN_REVISIONSubversion revision number that’s currently checked out to the workspace, such as “12345”SVN_URLSubversion URL that’s currently checked out to the workspace.

X

发表评论

电子邮件地址不会被公开。 必填项已用*标注