Discussion about this feature, as mentioned at http://youtrack.jetbrains.com/issue/TW-18911
Currently (at least in subversion) we can re-use the same build configuration for multiple branches by using a build parameter in the repository url, such as this:
This way we can ask TeamCity to build from different branches in the Custom Build Run dialog:
Seems that TC 7.1 already detects this pattern and shows branch info on the build status, altought I don't know why it shows in the xxx;xxx format.
So seems that some superficial support is there, but still far away from the Git or Hg, for example it will be better to choose which branch in a custom tab instead of relying on this customized parameter.
Anyone with experience with Perforce can please add some information, maybe something related to streams?
One possibility here would be to specify a pattern for the Subversion repository path - http://myserver/svn/projects/my_app/branches/(branch)/.* - this would mean you could watch the /projects/my_app/ folder for any changes, and when a change is detected whose checkin path matches the pattern, TeamCity could extract the branch name based on that pattern and use that in the builds and reports just as it does with Git.
I like the pattern idea, but to take care of the default Subversion repository structure, it should be possible to map them - something like this:
If the repository has a trunk at /repo/trunk and three branches at /repo/branches/feature1, /repo/branches/repo2, /repo/branches/repo3, the list of selectable branches will be "trunk", "feature1", "feature2" and "feature3".
What about VCS build triggers?