Of all the Extreme Programming practices, continuous integration is one of the least controversial – the benefits of an integrated, streamlined build process is something that software developers immediately recognise. However, as a project scales up in size and complexity, continuous integration can become increasingly hard to practice successfully. By focussing on the problems associated with a growing project, this paper describes a variety of strategies for successfully scaling continuous integration.


Integration Process Unit Test Acceptance Test Integration Server Code Base 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Fowler, M.: Inversion of Control Containers and the Dependency Injection pattern,
  2. 2.
    Fowler, M., Foemmel, M.: Continuous Integration (2001),
  3. 3.
    Beck, K., Fowler, M.: Planning Extreme Programming. Addison-Wesley, Reading (2001)Google Scholar
  4. 4.
    Mackinnon, T., Freeman, S., Craig, P.: Endo-Testing: Unit Testing with Mock Objects. Extreme Programming Examined. Addison-Wesley, Reading (2001)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2004

Authors and Affiliations

  • R. Owen Rogers
    • 1
  1. 1.ThoughtWorks, Inc.LondonUnited Kingdom

Personalised recommendations