I've archived an artifact as the last step of the build and it's available as something like this: https://xxx.ci.cloudbees.com/job/xxx/52/artifact/target/xxx-1.2.1-SNAPSHOT-r8304-20130807-1507-app.zip
How can I easily access the artifact in my promotion process? Please note that I need to access the specific build, not the latest successful one.
The goal of the promotion process is to copy the artifact to S3 from where our deployment job will further process it. So I might promote build #52 to development (copy it to a specific S3 bucket), later on promote build #50 to production and so on.
Ideally, I can access the artifact in a shell script to rename the file etc. Is there an environment variable to access the archived artifacts of a build, which I cannot find or how should this be done? $BUILD_URL
and $JOB_URL
are already specific to the promotion process and don't point to the build itself in shell scripts on the promotion job.
With the copy artifact plugin I can only copy artifacts from other builds in the promotion process, which I don't need to do.
I believe I have found the solution.
${PROMOTED_NUMBER}
Prerequisites
Promotion setup:
Setup up your promoted build with name and criteria as usual.
In the Actions section add the action Copy artifacts from an other project, and set these values.
${PROMOTED_JOB_NAME}
${PROMOTED_NUMBER}
path/to/your/artifacts/**
${BUILD_TAG}
Then add the actions you really want to do. For example add the action Archive the artifacts to save the artifacts. Remember to prefix your paths with ${BUILD_TAG}
e.g. ${BUILD_TAG}/path/to/your/artifacts/**
Copying artifacts
As you probably know by now, the promotion should not expect to have access the the content of the workspace of the build. It might be executed on a different server, and it might have access to no workspace at all or the workspace from an older or newer build. It is therefore required to copy the artifacts you want to use to the current workspace.
This is also the reason why the Target value is set. The workspace might be poluted with other builds or promototions. Setting target to ${BUILD_TAG}
Prevents any conflicts with files already in the workspace, by creating a folder unique to the promotion process.
${PROMOTED_*} variables
As you state the normal build variables refer to the promotion process itself, but The Promoted Build Plugin defines some environment variables referring to the actual build instead.
Permalinks
In a Jenkins context permalinks only refers to the special links that points to the latest build of some type or the latest promotion. That is why you will always get the latest version
In my version of Jenkins the dropdown is replaced with a textbox. Writing the URL to a specific build like http://jenkins/job/myjob/59/
is not recognized as one of the special permalinks, and the copying will thus fail.