I've been using the latest release of CruiseControl.NET (1.6.7981.1). It works fairly well, but the web dashboard is not the greatest and I dislike how the service refuses to start if any of the projects files have incorrectly configured XML.
What are my options? How about using the main CruiseControl instead? Will it play nicely with MSBuild? Will it format the MSBuild results reasonably like the CruiseControl.NET "MSBuild Report"? I see that it hasn't had any releases since September 2010. Yikes. Is it essentially fully baked?
CC.NET is really better than CruiseControl, and lightweight.
If you need to change, first let's write your requirements and constraints of such continuous integration tool.
If you just need something 'nicer', and easier to use, then consider switching to Jenkins, as the configuration is mainly done with a web interface.
If you need custom reports, custom email or custom statistics, then continue with CC.NET.
And remember that you should always use CCValidator.exe located in CC.NET install folder to validate your configuration file(s).
Switching from one CI tool to another is easy, as you already have all the scripts to execute.
As a long-time user of cc.net, I'd recommend switching to Jenkins or TeamCity. I really like TeamCity, but Jenkins is trivial to configure and get running.
