Feature branches in 7.1: Why does it build the default branch?

Hello,

We started using the new feature-branch feature in TeamCity 7.1 today.

We are working with a setup where each developer has a repository which he forks from the main repository. This means we have multiple VCS roots attached to the same build configuration. For each VCS root we have setup the branch specification "+:refs/heads/story-*".

This works fine, but when people update their master branch (just keeping up with upstream), then that is also built. Why is that? Shouldn't it skip non-feature branches?

I have trouble understanding the section "Multiple VCS roots" on http://confluence.jetbrains.net/display/TCD7/What%27s+New+in+TeamCity+7.1, especially the accompanying table.

4 comments
Comment actions Permalink

Hello,

is it correct that you attached several VCS roots pointing to the forks of the same repository to the single build configuration?

0
Comment actions Permalink

Yes. Is this the wrong way to do it? We are having some issues with branches not being checked out in the correct state.

0
Comment actions Permalink

Intended use is the following. Build configuration has only one VCS root attached, VCS root points to the main repository. Developers have clones of the main repository to theis machines. You don't need to register these clones inside TeamCity. To use feature branches developer creates a branch, matched by branch spec, do some work and push it to the main repository. Then TeamCity detects this branch and runs the build.

0
Comment actions Permalink

Thanks for the clarification!

The problem with the solution you describe, is that as an organization we don't give each developer write access to the main repository on Github. Each developer has only write access to his/her repository, which is where feature branches are being pushed and where pull requests can be made from.

I think I will create a build configuration for each developer (using a template).

0

Please sign in to leave a comment.