Should I each time change my teamcity configuration after creating a new branch?

I am following the following structure to re-structure my source-control project. Now I am also using TeamCity  as my CI server. The configuration in TeamCity points to a specific tfs  path in order to build the project. If I create a new branch, then I  would also need to change the TFS path and eventually create a new  TeamCity configuration. I am not sure if this is the proper way to do  this. How do you manage your teamcity configuration when you branch?

4 comments
Comment actions Permalink

For this reason, I use CI only on the main branch.

0
Comment actions Permalink

How do you deploy the branches to the test server then?

0
Comment actions Permalink

Let me rephrase my solution...

I have a build configuration for each version/branch combination. For example, if you have version 2 and 3 and branch Release and Team, I would have four build configs for Ver 2 Release, Ver 2 Team, Ver 3 Release, Ver 3 Team.

Developers branch out from the Team branch, then merge into the Team branch. Therefore, CI is not available to each invidicual developer branches. Team branch, however, is monitored through CI and kept stable.

Not sure if it answers your question.

0
Comment actions Permalink

Hi

We have a feature request TW-4778 for this, you can vote.

At the moment you can create a build configuration template to simplify cloning, and specify branch names as a parameter.

Michael

0

Please sign in to leave a comment.