Question

We’d like to implement CI using TeamCity.

We use Git for source control and would like to make use of the “pre tested commits” or “personal builds” feature of TeamCity.

Does anyone have experience with the VS plugin for Teamcity?

As far as I’ve seen, it only supports Subversion, no word about Git.

Anyone used this setup with any success?

Answer 1

As explained in Pre-tested “Commits” using Git by JoergM, you can emulate a solution similar to the TeamCity6.x “Personal builds on branches”, by using personal repos:

.

There is one central Git-repository that only contains pre-tested changes. I call this “Green Repository” because it should only contain changes that lead to green builds.
Every developer pulls from this repository but nobody is allowed to push to it.

Instead everybody has a personal repository (think fork if you were on GitHub). The CI Server watches those personal repositories. After a commit it starts the compile and test. If that was successful it pushes the changes to the Green Repository.

JoergM adds:

The question is whether we will continue using our own solution or switch to the new feature of Teamcity.
So far I can’t see any advantage of the Teamcity feature.
With our solution we are even more flexible in regard of branch design.

This kind of setup is similar to what I described in “What is the cleverest use of source repository that you have ever seen?“.