CruiseControl .NET
I've been writing NAnt scripts again for the last couple of days, and getting a CI system in place, but this time using CruiseControl, rather than Draco. I've been pleasantly surprised by CC - it was a breeze to set up (wish I could say the same about NAnt), the documentation was excellent, and it has lots of extra features that Draco lacks (an asp.net dashboard and a tray app that provides build status notifications), and integration with a variety of source control tools (including ClearCase, which is what I've been integrating with).
If you haven't looked into CI, then you first of all need to get intimate with NAnt (ignoring MSBuild for the time being). NAnt can be downloaded from SourceForge; there should be (just enough) documentation to help you get up and running. You're wise to use the Solution task in the NAntContrib project to automatically generate a NAnt script at build time from your .net solution file - this saves you having to constantly update the script when devs add or remove projects.
Once you've got this working, you should look into integrating NDoc (to automate the creation of your code documentation from C# comments), NUnit or NUnitForms (to run your unit tests), and FxCopCmd for lower level code analysis.
Once you've automated all that in your NAnt script, you can get CruiseControl working relatively easily. Best approach is to get it all working locally, then migrate it all to a build server (make sure it has IIS and asp.net installed for the CC Dashboard).

0 Comments:
Post a Comment
<< Home