Summary
In this chapter you’ve learned the value of Continuous Integration. If one thing is clear, it is that the success of CI depends heavily on making developers embrace the concept of not holding on to changes for longer than a day and that a test-first approach is the easiest way to have a measurement of when to check code back in. Tools like CruiseControl replace the hodgepodge of ad hoc tools and shell scripts that developers cobbled together in the past to accomplish CI. Automation in the case of CI is the key to adoption. The hours spent setting up a build server will save you and your team countless hours of productivity loss in the future.
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.
Rights and permissions
Copyright information
© 2006 Brian Sam-Bodden
About this chapter
Cite this chapter
(2006). Continuous Integration. In: Beginning POJOs. Apress. https://doi.org/10.1007/978-1-4302-0142-7_9
Download citation
DOI: https://doi.org/10.1007/978-1-4302-0142-7_9
Publisher Name: Apress
Print ISBN: 978-1-59059-596-1
Online ISBN: 978-1-4302-0142-7
eBook Packages: Professional and Applied ComputingApress Access BooksProfessional and Applied Computing (R0)