How to use branches with multiple projects and Teamcity

Question

I am looking for best practice for the following situation:

I have one bll / dal project and UI tree projects that use the bll / dal project. First we put all this in one trunk folder in the SVN repository. We use userbranches, so each userbranch had all the source code.

Now we started using TeamCity as a build server, and we wanted each project to have its own version of the product. Thus, we divided the body into different SVN repositories (each project on a different SVN), so that each project has its own version number in its version of the product.

We have continuous integration and continuous deployment for each project on a team basis. 4 gives 8 configurations

Now we also want for each CI user its branch. But now we have to make a user branch for each project, so there will be 4 user branches for each user. This also suggests that we need to configure 4 CI configurations for each user in TeamCity ...

Now I'm just wondering if this is a good approach or are there better solutions ...?

Thanks in advance.

Bruno

Answer 1

Since you are looking for best practices, I believe that it is never good to have separate branches for each user (developer?), And "CI" in this sense is not CI at all - it is more a personal assembly than anything else.

For branches in TeamCity, you can add the build configuration of a specific branch to Project. For example, if there is a build configuration, you can add build-release for the release branch, etc.

Answer 2

Perhaps this new feature in 6.5 EAP might help you (parameterized CVS roots).