全部博文（33）
分类： Delphi
2012-03-22 15:11:14
When a Hudson job executes, it sets some environment variables that you may use in your shell script, batch command, Ant script or Maven POM . The following table contains a list of all of these environment variables.
| Environment Variable | Description |
|---|---|
| BUILD_NUMBER | The current build number, such as "153" |
| BUILD_ID | The current build id, such as "2005-08-22_23-59-59" (YYYY-MM-DD_hh-mm-ss) |
| JOB_NAME | 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 Hudson Dashboard main page. |
| BUILD_TAG | String of hudson-${JOBNAME}-${BUILD_NUMBER}. Convenient to put into a resource file, a jar file, etc for easier identification. |
| 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. |
| 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. |
| WORKSPACE | The absolute path of the workspace. |
| SVN_REVISION | 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. using SVN_REVISION_n to specify . n based on index 1 modules |
| 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. |
