Continuous Integration
Apress eBooks · 2006
SummaryIn 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.