Figure 10.8. Configuring a Run parameter
The URL (which will look something like http://jenkins.myorg.com/job/game-of-life/197/)) can be used
to obtain information or artifacts from that build run. For example, you could obtain the JAR or WAR
file archived in a previous build and run further tests with this particular binary in a separate build job.
For example, to access the WAR file of a previous build in a multimodule Maven project, the URL
would look something like this:
http://buildserver/job/game-of-life/197/artifact/gameoflife-web/target/
gameoflife.warSo, using the parameter configured in Figure 10.8, “Configuring a Run parameter”, you could access
this WAR file using the following expression:
${RELEASE_BUILD}gameoflife-web/target/gameoflife.warFile parameters let you upload a file into the build job workspace, so that it can then be used by
the build script (see Figure 10.9, “Configuring a File parameter”). Jenkins will store the file into the
specified location in the project workspace, where you can access it in your build scripts. You can use
the WORKSPACE variable to refer to the current Jenkins workspace directory, so you could manipulate the
file uploaded in Figure 10.9, “Configuring a File parameter” by using the expression ${WORKSPACE}/
deploy/app.war.
Figure 10.9. Configuring a File parameter
10.2.4. Building from a Subversion Tag
The parameterized trigger has special support for Subversion, allowing you to build against a specific
Subversion tag. This is useful if you want to run a release build using a tag generated by a previous build