Vcs Labeling
Build feature enabling automatic VCS labeling in a build.
Example. Upon finishing of a successful build, add a tag with name 'teamcity-build-%system.build.number%' to the VCS repository of the VCS Root with specified id. Note: parameter reference %system.build.number% will be replaced with the build number of the build. See also predefined parameters.
buildType {
// Other Build Type settings ...
features {
// Other Build Features ...
vcsLabeling {
vcsRootId = "< id of a VCS root>"
labelingPattern = "teamcity-build-%system.build.number%"
successfulOnly = true
}
Content copied to clipboard }
}
Example. Create labels with a custom labeling message. Note: parameter references will be replaced accordingly. See also predefined parameters.
buildType {
// Other Build Type settings ...
features {
// Other Build Features ...
vcsLabeling {
vcsRootId = "< id of a VCS root>"
messageFormat = """
TeamCity build: %system.build.number%
Changelist number: %build.vcs.number%
""".trimIndent()
}
Content copied to clipboard }
}
See also
Properties
Branch filter specifies in which branches sources should be labeled
A pattern for labels to use. If not specified, then the default pattern is used: build-%system.build.number%.
Customize the VCS type-specific labeling message format. Parameter references are supported. By default, the labeling message is: automatically created by TeamCity VCS labeling build feature
Whether only successful builds sources should be labeled
Id of the VCS root which sources should be labeled. Use the constant "ALL" to label all VCS roots.
Functions
Copies parameters of this object to the specified target
Creates an instance of this build feature via reflection using a no argument constructor, used during copying. Throws an error if this class doesn't have a default constructor. Subclasses can override it to create an instance without using a default constructor.
Validates this object and reports found errors to the provided consumer