Multiple repositories for Branch Remote Run Trigger

In our organization we have a github-style setup with forks, e.g. we have the following repositories:

Main repository, production ready: git@github.com:companyname/code.git
Developer repository 1: git@github.com:developer1name/code.git
Developer repository 2: git@github.com:developer2name/code.git
etc.

We have already set up TeamCity to build and deploy using the main repository.
Now when people push new branches to their individual developer repositories, we would like to use the feature "Branch Remote Run Trigger". We would like to test quickly if the branch compiles and passes unit tests.

However it seems that we need to make a new build configuration for each VCS root, or am I mistaken?

4 comments
Comment actions Permalink

You can attach multiple VCS roots to a single build configuration, and the trigget will watch for changes in all of them.

0
Comment actions Permalink

Thanks.

The build configuration works, but always shows "no finished builds" (but each developer can see his own builds). Is it not possible to see other developers builds?

0
Comment actions Permalink

Nevermind, we have upgraded to TeamCity 7.1 with the new feature branch feature; seems to work a lot better :-)

0
Comment actions Permalink

I'm glad it works for you.

Answering the question, by default each user sees his own personal builds only. But it can be changed on profile page by Show all personal builds option.

0

Please sign in to leave a comment.