How does your continuous integration work?

Question

I'm building a CI server and would really appreciate to get real experiences, and an overview on what are people using.

So, what are your build processes? Is there something like:

• one hourly for code and tests,
• another daily for build msi and code metrics,
• etc.,

and also, what does your complete build process use? Do you use something like:

• team city,
• msbuild,
• nunit - for tests,
• ncover - for test coverage,
• ndepend - for code metrics,
• sandcastle - for documentation by the code comments,
• testcomplete - for QA tests,
• etc.?

Share! ;)

Answer 1

We had a similar conversation at the most recent CITCON North America (Continuous Integration and Testing conference) where we all shared our experiences and tried to put together a road map from simple CI to very built out CI and release systems.

The original conference notes are here. Along with a Flickr photostream. A cleaned up version is available at the urbancode blog as well.

The Aussies revisited the topic at CITCON Brisbane and a pencast of that is available

Hope some of those resources are useful.

Answer 2

For Java, we have an instance of Hudson checking for commits in the SVN repository, for every commit there is a build in which everything is compiled and all the test units are run using Maven2. Also the Hudson is connected to an instance of Sonar which tell us stats about coding style and testing coverage.

Sonar screenshot http://nemo.sonarsource.org/charts/trends/60175?sids=1024412,1025601,1026859,1073764,1348107,2255284&metrics=complexity,mandatory%5Fviolations%5Fdensity,lines,coverage&format=png&ts=1244661473034

Sweet :)