Abstract
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.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
Fowler, M.: Inversion of Control Containers and the Dependency Injection pattern, http://martinfowler.com/articles/injection.html
Fowler, M., Foemmel, M.: Continuous Integration (2001), http://martinfowler.com/articles/continuousIntegration.html
Beck, K., Fowler, M.: Planning Extreme Programming. Addison-Wesley, Reading (2001)
Mackinnon, T., Freeman, S., Craig, P.: Endo-Testing: Unit Testing with Mock Objects. Extreme Programming Examined. Addison-Wesley, Reading (2001)
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2004 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Rogers, R.O. (2004). Scaling Continuous Integration. In: Eckstein, J., Baumeister, H. (eds) Extreme Programming and Agile Processes in Software Engineering. XP 2004. Lecture Notes in Computer Science, vol 3092. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-540-24853-8_8
Download citation
DOI: https://doi.org/10.1007/978-3-540-24853-8_8
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-22137-1
Online ISBN: 978-3-540-24853-8
eBook Packages: Springer Book Archive