As we approaching to TeamCity 7.1 release which is planned for the end of July, beginning of August, we concentrate our efforts on polishing new features and bugfixing. This EAP build does not have many new features besides some significant improvements in feature branches.
We've improved a lot in this area.
In previous EAP you could use * in branch specification, like this:
For TeamCity this rule means:
refs/heads/master, TeamCity will set
masterlabel to build
This rule works well, but what to do if you can't use * but still want shortened branchy labels in builds? To address this problem we extended syntax of branch specification and now it allows this:
In this case TeamCity will use label
7.0 for builds from
refs/heads/release-7.0 branch and
7.1 for builds from
Read more about branch specification syntax in our documentation
In a build configuration with branches enabled, TeamCity will assign branchy label to builds from default branch too:
Want to see an overview of what is going on in each active branch? There is a new build configuration tab to answer exact this question: