As you might know, TeamCity comes with such feature as build tags – do not confuse with supported VCS tags, because that’s an entirely different story. You can assign any number of tags for a single build, and then use them to organize your build history, or quickly navigate to the tagged builds. There is nothing tricky about that, but one might ask himself when these tags can be helpful.
Well, here is an example. Suppose, after some time of developing, your project manager decides, that you’ve finally got a stable build that can be considered a release candidate, or eap. He can mark this build with “EAP” tag, and thus, guys from QA won’t need to search through the whole build history to find the build they should carefully look at. They’ll just need to filter the history by this tag, or simply type “EAP” in the search field.
You can also leave a comment on any build, providing some extra notes about it; and just as with the tags, you can later on search for the build by the comment. Hope, you’ll like it.
Feedback is appreciated as usual.
Tags.NET 5.1 agent agent pool Amazon EC2 API artifacts automation bug-fix build configuration build failure conditions build runner custom reports dependencies dotCover Full City Tech Git Gradle guest post inspections intellij idea investigation Maven mercurial meta-runner notifications NuGet NUnit octopus deploy parameters paul stovell PHP plugin plugins R# RC ReSharper REST API TeamCity TeamCity 7.1 unit testing Unit Tests Visual Studio Webinar Wes McClure
Other JetBrains Blogs