posted 16 years ago
Absolutely. Building your software is a fundamental software development practice and we describe good approaches and bad approaches using examples for different development platforms. Continuous Integration is different than just a daily build in that it increases the emphasis on getting the entire development team to follow core practices (such as committing code to the repository often, preventing build breakages, fixing integration build breakages quickly, and creating a truly automated build). In chapter 1, we go over the main parts of setting up a CI system and then go over the principles and developer practices, risks that can be reduced on your project. The latter chapters cover creating a more full-featured CI system. There are pointer to plenty of resources throughout the book (and Appendix A gives a thorough list of resources) and the integratebutton.com companion website has videos for each of the practices in the book that support the text.
Co-author of <a href="http://www.amazon.com/gp/product/0321336380/" target="_blank" rel="nofollow">Continuous Integration: Improving Software Quality and Reducing Risk </a> <br />(Addison-Wesley Martin Fowler Signature Series, 2007). Companion website for the book is <a href="http://www.integratebutton.com/" target="_blank" rel="nofollow">IntegrateButton.com</a>