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.
Feature branches
We've improved a lot in this area.
Extended branches specification syntax
In previous EAP you could use * in branch specification, like this:
For TeamCity this rule means:
- watch changes in all branches starting with
refs/heads
- set a branchy label on build with name which is a part of rule matched by *, i.e. if branch name is
refs/heads/master
, TeamCity will setmaster
label 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 refs/heads/release-7.1
.