Publisher: Addison-Wesley, 2007, 283 pages
For any software developer who has spent days in integration hell, cobbling together myriad software components,Continuous Integration: Improving Software Quality and Reducing Risk illustrates how to transform integration from a necessary evil into an everyday part of the development process. The key, as the authors show, is to integrate regularly and often using continuous integration (CI) practices and techniques.
The authors first examine the concept of CI and its practices from the ground up and then move on to explore other effective processes performed by CI systems, such as database integration, testing, inspection, deployment, and feedback. Through more than forty CI-related practices using application examples in different languages, readers learn that CI leads to more rapid software development, produces deployable software at every step in the development lifecycle, and reduces the time between defect introduction and detection, saving time and lowering costs. With successful implementation of CI, developers reduce risks and repetitive manual processes, and teams receive better project visibility.
The book covers
Well, nothing new under the sun here. This is what most people did in operating system development circles in the beginning of the 90-ties.
Feels like another try to introduce something that already exists to the ignorant masses of new programmers that believe they invented everything in development…
Add to this that it is not very enlightening and fails to make a good introduction to the reason why continuous build and test cycles are a very good idea. OK, it is not bad, but it could have been so much more.