Continuous integration (CI) is an agile software development practice that involves automatically building and testing code changes frequently, such as daily, to catch errors early. CI provides benefits such as easy identification of broken builds, minimized integration effort, and early detection of failures. It establishes confidence through widespread best practices and reuse of existing build scripts. Popular open-source CI tools include Jenkins, TeamCity, CruiseControl.NET, and Bamboo, with options for both free and paid use.

1. WHY CI?

2. THE JOEL TEST (AUGUST 2000)
12 STEPS
2. Can you make a build in one step?
3. Do you make daily builds?
5. Do you fix bugs before writing new code?

3. AGILE
1. CI is a less controversial agile practice
2. Rapid delivery goal
3. Synergistic effect with Unit Testing and Coding
Standards

4. FIXES PROBLEMS
broken build
lack of integration
works for me!
find and fix bugs

5. BENEFITS
easy to know build state
minimize integration effort
static code analysis
easy to configure
gather statistics
early prediction of fail

6. WHY ELSE
widespread best practice
establish confidence
reuse existing MSBuild scripts

7. STATIC CODE ANALYSIS
FxCop, StyleCop, CheckStyle
NDepend
Simian (code duplicates)
NDoc, Sandcastle

8. TOOLS
Team Foundation Server
Bamboo
QuickBuild, Continuum
CruiseControl/CC.NET
Jenkins/Hudson
TeamCity

9. CC.NET

10. CC.NET
Cannot add/edit a project via web-interface

11. JENKINS

12. JENKINS

13. JENKINS
Big setup effort

14. TEAMCITY

15. TEAMCITY

16. TEAMCITY
Free up to 20 build configurations

17. QUESTIONS?