In the spirit of keeping my SVN box clean and ready for deployment, I used the following version control model . For an impatient, the basic concept is that you create development branches for the actual development and leave the trunk clean and ready for deployment at any time (no debris in the trunk).
In addition to this, I am configuring TeamCity for continuous integration. In TeamCity, I would like all the development branches, as well as the deployment branch (trunk in my case) to build correctly and pass all unit tests.
This may be a stupid question, but not too familiar with TeamCity, should I create a new TeamCity project for each branch? In particular, in the deployment branch there are several additional rules than the development branch. For example, releases must be saved in directory versions on the file system (e.g. C: \ Projects \ MyProject \ 1.0.187 ..., C: \ Projects \ MyProject \ 1.0.188 ...) to provide easy binary access files at any given time. On the other hand, saving versions of assembly instances in the development branches is not required and will waste hard disk space.
In TeamCity, I would prefer to see only one project for each software project. In other words, if my company is working on X number of development projects, I would prefer to see that the project is indicated only once, and not X * 2 (provided that each project has only two branches).
senfo source
share