Child pages
  • Faradi 7.1 EAP (build 23833) Release Notes
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

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 set master 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.

Read more about branch specification syntax in our documentation

Branchy labels for builds from default branch

In a build configuration with branches enabled, TeamCity will assign branchy label to builds from default branch too:

Branch selector on overview and project page

Branches tab in build configuration

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:

Builds on change log graph

Branch parameters

For Git & Mercurial TeamCity provides additional build parameters with names of VCS branches known on the moment of build starting. If build took a revision from branch refs/heads/bugfix TeamCity will add configuration parameter with name:
teamcity.build.vcs.branch.<simplified root name>

In addition to this parameter name VCS branch is now shown on build changes page as well in revisions table:

  • No labels