4

I'm looking for a best practice for the following situation:

I have one bll/dal project, and tree UI projects that uses the bll/dal project. In the beginning we putted it all in one trunk folder on a SVN-repository. We are using userbranches, so each userbranch had all sourcecode.

Now we started using TeamCity as a buildserver, and we wanted that each project has it own product version. So we splitted up the trunk on different SVN repositories (each project on another SVN), so that every project has it own revisionnumber in its productversion.

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

Now we want also for each user a CI of his branch. But now we have to make for each project an user branches, so that will 4 user branches for each user. This involves also that we need to configure 4 CI-configuration for each user on TeamCity...

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

Thanks in advance.

Bruno

bruno
  • 1,830
  • 2
  • 22
  • 36
  • First you should forget about "revisionnumber" you should use tags instead. Furthermore you should think about a dependency solution, depending in which language you are developing (Java=> Maven, Gradle, Ivy) to solve your dependency problems. – khmarbaise Apr 13 '11 at 11:58

2 Answers2

3

Maybe this new feature in 6.5 EAP may help you (parametrized CVS roots).

Chris Frederick
  • 5,482
  • 3
  • 36
  • 44
Riccardo Cossu
  • 2,699
  • 1
  • 28
  • 47
2

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

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

manojlds
  • 290,304
  • 63
  • 469
  • 417