CruiseControl was created in the early 2000s when Martin Fowler wrote an article about continuous integration (CI) and its benefits. This prompted Thoughtworks to develop CruiseControl to automate the CI process on a project they were working on. CruiseControl proved popular and was adopted by many other projects, leading to the creation of connectors to integrate it with various code repositories. Over time, CruiseControl expanded to support additional programming languages through projects like CruiseControl.Net and CruiseControl.rb. While CruiseControl helped advance the practice of CI, newer tools now exist to continue improving the CI process.

1. Continuous Integration and CruiseControl history Paulo Caroli and LuizaPagliari Many thanks to Martin Fowler and colleagues at Thoughtworks!

3. C3 project 4 Dev pairs (Kent, Martin, Ward…) Smaltalk / Genstone Manual Integration Integration server Developer name on post-it Red / Yellow / Green

4. C2 wiki XP is being born

5. XP Explained book released Project A Martin, Ward and TW Java Integration was a 2 week exercise

6. < Early 2000 > Project A goes for XP 50 developers, many teams Java / Star Team / before ant While (true) { sleep upload? build test }

7. < Late 2000 > Martin’s CI article Project B Repeat the CI automated idea CruiseControl is born

8. Project C, D … X Connectors to many repositories Many contributors

9. CI practice really picking up TW in a .Net project CruiseControl.Net

10. TW in a Ruby project CruiseControl.rb

11. This talk about CruiseControlhistory (FISL 2010 conference) Many good options! Next generation of tools