I searched and saw similar questions have been asked before. Hopefully, my question has novelty enough to deserve an answer :)
We had been using TeamCity 7.x with SVN as source control system for a long time and it works well enough. Recently we upgraded to TeamCity 8.1.1 and now I am trying to create build configurations for our projects using Git. The first obvious change is you are not able to create independent VCS roots, rather each VCS root is attached to a project.
So I create a project "My Project" under root and created a Git VCS root pointing to:
The default branch is set to:
And Branch specification is empty.
Then I created a build specification for the master branch and it started building fine. Now I need to create another build pointing to 10.0.0 branch. To minimize overhead, I want to share the same VCS root, but definitely want a separate build configuration (with separate build numbers).
I cannot figure out how do I accomplish this. If my source control was SVN, I would have just created another build configuration with the common VCS root, and edited checkout rules pointing to trunk or specific branches (effectively allowing me to create different build sharing same VCS root).
Because of the way Git works, customizing checkout rules to point to specific branch is not feasible. The branch specification parameters which ideally should have belonged to a build configuration need to be set at VCS root level.
Did I miss something or doing something wrong. Is it possible to share a Git VCS root with different build configurations pointing to different git branches.
Message was edited by: Rahul Singla