Feature branches with several build configurations and multiple VCS roots

Hi,

We have the follwoing scenario:

We have a bunch of build configurations.Those build configurations are linked to other build configs with snapshot and artifact dependencies. The build configurations are building from different repositories but the branch names in the repos are (or can be made) identical

BuildConfig 1 (VCS Root 1)
                  ^
                  |
                  |
--------------------------------------------------------------------------------------------------------------------------------
| BuildConfig 2 (VCS Root 2)  | BuildConfig 3 (VCS Root 3) | BuildConfig 4 (VCS Root 4) |
--------------------------------------------------------------------------------------------------------------------------------
                  ^
                  |
                  |

BuildConfig 5 (VCS Root 1)

So as you can see BC 1 and BC5 share the same vcs root. the intermediate BCs have different build roots.

Now we want to make use of TeamCities Feature Branches Feature.

Hence we configured the Branch specification in the vcs root configuration page. When a build trigger starts a build for BC5 on a given branch we would hope that the same branch is used in all other build configs as well. However this is not the case.

We are running on TeamCity 8.1, all VCSs are git

Any help is apprechiated!

Cheers,

Bernd
2 comments
Comment actions Permalink

Hey there.

This question remained unanswered for a long time. Did anyone come with a solution for this issue. I'm having a similar setup and I can't seem to find a solution for it

0
Comment actions Permalink

Hi,

if the branches are named the same and they are connected via snapshot dependencies, the same branch should be used for all builds, as long as it's available: https://confluence.jetbrains.com/display/TCD10/Working+with+Feature+Branches (we call it logical branch name).

0

Please sign in to leave a comment.