Several people at the p&p Summit had questions around CI. I thought I’d follow it up with a post on with some useful links etc.
I’ve used CI on a couple of teams at Microsoft, notably Visual Studio Tools for Office and the patterns & practices group. While we were at p&p Alan Ridlehoover and I gave a talk about CI for the engineering excellence group here at Microsoft and there lots of posts about it on my blog in the Continuous Integration topic, especially the thoughts on CI post.
I have a paper accepted to Agile 2008 documenting the cost/benefit of CI. Once the conference has published it a copy of the paper and accompanying talk will be available on my publications page. If you attended my talk at the p&p Summit this is where the 40% time saving over a non-CI based check-in approach comes from.
CI can be used on large projects too, like Visual Studio Tools for Office where it was a major part of our strategy to be more agile using feature crews and involved a lot of integration between branches – paper here:
There’s some more general guidance from Microsoft on how to use TFS for branching, which may be a key part of your divide and conquer strategy with small agile teams contributing to a larger project:
There’s also a book on Continuous Integration by Paul Duval. I have the book but haven’t had time to read it through yet, it looks very promising. I kep meaning to finish it and write a review. When I do it’ll be published here.
At p&p we’ve used CruiseControl.NET for our CI server and for small teams wanting a lightweight approach that can be quickly setup by one person in under a day then CC.NET is ideal. For larger environments where tight integration between the CI build and source code control then Visual Studio Team System’s Team Foundation Build feature may be more appropriate.
If anyone has any other resources they found useful in getting their CI build off the ground then please add them in a comment!