|You are viewing documentation of TeamCity 5.x, which is not the most recent released version of TeamCity. Please refer to the listing to choose another version.|
To label a finished build manually:
The labeling process takes place after the build finish and doesn't affect the build status. If the label fails it will not change the build's status.
VCS labeling is supported for ClearCase, CVS, Perforce, StarTeam and Subversion.
Subversion VCS roots need additional configuration for VCS labeling to work. The labeling rules need to be specified to define the SVN repository structure.
Labeling rules are specified as newline-delimited rules each of uses the following format:
The repository paths can be relative and absolute (starting from "/"). Absolute paths are resolved from the SVN repository root (the topmost directory you have in your repository), relative paths are resolved from the TeamCity VCS root.
When creating a label, the sources residing under
For example, there is a VCS root with the URL svn://address/root/project where svn://address/root is the repository root, and the repository has the structure:
In this case the labeling rules should be:
VCS Labeling Failure Notifications
TeamCity starts the VCS labeling process, when the build is finished. Thus VCS Labeling does not affect the build status, and therefore is not a standard notification event. However, TeamCity allows notifying about labeling failure.