Recommendations regarding Continuous Integration s

Question

We are currently evaluating different applications that interface with Visual Studio 2008 (C#) and Subversion to do automated builds of our core libraries. We are hoping to have nightly builds performed and either email the list of changes made to each developer or have the latest versions be pushed to each workstation. What has been your experience with these tools and what are some recommendations?

---

Suggested software

• Cruise Control .NET
• Hudson
• TeamCity

Suggested articles

• Continuous Integration: From Theory to Practice 2nd Edition (CC.net)
• Automating Your ASP.NET Build and Deploy Process with Hudson

Answer 1

I've used cc.net with nant and msbuild with great success, would highly recommend it.

Answer 2

A couple of tidbits about working with cc.net and msbuild. If you are building C/C+= projects, msbuild is, um, unreliable at least with VS 2005 (and perhaps earlier). I have not tested with VS 2008. We found that sometimes msbuild would work properly, sometimes not. In trying to solve the problem, we found vcbuild.exe which seems to work well in place of msbuild when building C/C++ solutions.

Answer 3

Hudson is the easiest continuous-integration / daily-build tool I've seen. Not sure if it meets all your requirements.

Answer 4

I use CC.Net along with SubVersion and MSBuild to accomplish this. Here is a great guide for implementing this which I followed on found very helpful.

Answer 5

Take a look at the JetBrain's (guys behind ReSharper) TeamCity

Answer 6

If you are using trac for issue tracking, the bitten plug-in works well. It's not platform specific (we run it on both Windows and Linux at work, with msbuild/mstest and make/gcc/cpptest respectively).