Overview
The apply tag post build action can be used to tag (or label) the built revision when a build completes. When the action is executed, it will apply a tag to all source files used in the build at the revisions that were built. Typical use cases include:
- tagging all builds with the project name and build number: so that your SCM has a record of all built revisions
- maintaining a "last known good" tag: by tagging only after successful builds with a moving tag (see the "move existing tag" option below)
Configuration
tag name
The name of the tag to apply, which may include references to the following variables:
| Variable |
Description |
| number |
The build number or id for the build. |
| project |
The name of the project built. |
| specification |
The name of the build specification built. |
| status |
The build status as a lower case string. |
Variables are refered to using the ${...} syntax, as used in pulse files.
 | Build properties
Build properties defined on the build specification are also available. |
Examples
A tag for every build, with unique build details in the tag name:
A moving "last-known-good" tag for the project (see also the "move existing tag" field below):
move existing tag
If checked, an existing tag with the same name will be moved to the build revision. If this option is not selected and the tag name is the same as an existing tag, the existing tag will remain unchanged and the action will fail.
