Jenkins：不同job之间传递参数

转载地址：http://blog.csdn.net/itfootball/article/details/45060331

有的时候不同job直接需要传递一个文件名或者路径，这个时候我们不需要传递文件实体，那这个路径如何传递呢？比如有如下两个项目，我想把A的工作目录传递给B，让B使用。 

A job配置

首先需要安装一个Parameterized Trigger Plugin插件：

安装后重启。

在A项目配置面板中Post-build Actions选项中选择Trigger parameterized build on other projects 
我选择的参数为预定义参数，如果想知道有哪些与定义参数，可以在Build模块下选择Execute shell

选在文本框下的the list of available environment variables 选项，可以查看如下信息：

The following variables are available to shell scriptsBUILD_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)BUILD_DISPLAY_NAME    The display name of the current build, which is something like "#153" by default.JOB_NAME    Name of the project of this build, such as "foo" or "foo/bar". (To strip off folder paths from a Bourne shell script, try: ${JOB_NAME##*/})BUILD_TAG    String of "jenkins-${JOB_NAME}-${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.NODE_NAME    Name of the slave if the build is on a slave, or "master" if run on masterNODE_LABELS    Whitespace-separated list of labels that the node is assigned.WORKSPACE    The absolute path of the directory assigned to the build as a workspace.JENKINS_HOME    The absolute path of the directory assigned on the master node for Jenkins to store data.JENKINS_URL    Full URL of Jenkins, like http://server:port/jenkins/ (note: only available if Jenkins URL set in system configuration)BUILD_URL    Full URL of this build, like http://server:port/jenkins/job/foo/15/ (Jenkins URL must be set)JOB_URL    Full URL of this job, like http://server:port/jenkins/job/foo/ (Jenkins URL must be set)SVN_REVISION    Subversion revision number that's currently checked out to the workspace, such as "12345"SVN_URL    Subversion URL that's currently checked out to the workspace.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33

ok,回到正题，具体配置如下：

我将A项目的工作目录传递给了自定义参数TEST_WORKSPACE.到这里A项目的配置就完成了。

B job配置

我们在A项目配置的TEST_WORKSPACE参数，如果在B job中使用，首先我们在配置界面中，勾选The build is parameterized。具体配置信息如下所示：

这样我们就在当前工作环境中得到了由A传递过来的参数。至于你怎么使用，那是你的事了。比如我在shell脚本中首先切换到该目录下(需要在一台机器上)，然后在A项目的工作目录下生成一个hello.txt文档，我们可以在shell命令下配置如下信息：

ok，配置完成了，这个时候我们构建A，看看能不能让B在A的工作目录下生成一个hello.txt文档。

Done!