Redefine Your Build Process with Continuous Integration

A growing number of development shops are adopting Continuous Integration (CI) as a best practice, and many more would get on the wagon if the cost of adoption was lower. It can take a veteran programmer a couple of days to get a basic CI server up and running; a neophyte might take up to a week.

In the March 2008 issue of MSDN Magazine, Jay Flowers explores the work required to set up and use a CI server and various solutions that help get the work done. Jay first creates a CI server manually using CruiseControl.Net, MSBuild 2.0, MbUnit, and WatiN, then shows you how to use an open source project called CI Factory to do the same thing with far less effort.

Don't forget to browse the sample code in our online code library.

For more articles on testing, be sure to check out our MSDN Magazine archives.


Comments (0)

Skip to main content