I've been goofing around with TeamCity over the last week. After reading some posts about TeamCity (1)(2), I decided to give it a try. In my continuous quest to eliminate the amount of XML programming in my life, I decided to replace my current CruiseControl.NET setup for my home project with TeamCity.
I couldn't believe how easy it was. I installed the server and got my first project up-and-running in about 15 minutes. At first, I was in complete denial. I must have done something wrong here. Then it hit me. This is how its supposed to be. TeamCity is what TFS and CC.NET should be like when they grow up. Don't take my word for it, take a look for yourself:
Sweet statistics huh? Setting up a new build is really simple.
Not everything is sunshine and happiness though. The shortcomings I encountered up till now are:
- No out-of-the-box support for NUnit 2.4. I hope that the brilliant people at JetBrains put out an update soon.
- No support for code coverage whatsoever (at least, I couldn't find it in the docs or on the web). Bummer.
Opposed to these shortcomings, there is a quite an impressive feature list for both Java and .NET:
I still have to take a look at the Duplicates Finder as it looks great too.
Now here comes the good news. You can download the professional edition for free! You can create 20 build configurations and make use of three different build agents which should be more than enough for small teams.
After becoming a real Resharper addict (can't use Visual Studio without it), I'm now becoming a slave to TeamCity as well. I've converted all my home projects, and life has never been better. Till next time.
