This week's book giveaway is in the Other Open Source APIs forum. We're giving away four copies of Storm Applied and have Sean Allen, Peter Pathirana & Matthew Jankowski on-line! See this thread for details.
For sure it�s a must-have for lead developers who need to set up a Continuous Integration mentality and environment, but I was wondering what do you think about dev teams with an already existing and everyday used CI environment, could they use the book as a �check-list� to see if the CI is used "correctly" or if there's something missing?
could they use the book as a �check-list� to see if the CI is used "correctly" or if there's something missing?
I think this would be a good way to utilize the book and, in many ways, this is how I organized it. At the beginning of (and throughout) the writing process, I thought to myself "if I were to list the effective practices I've used on projects, which would I choose?" There are 46 CI-related practices in the book. Most of the 46 practices are chapter subheadings and are based on this list of practices that are useful from our experiences. Of course, not everything on this list of effective practices made it to the book because certain practices weren't relevant to Continuous Integration. And, I definitely don't think you need to implement all of the practices from the book to be successful at CI, but "Continuous Integration" demonstrates the possibilities of what you can implement using examples.
For dev teams with an existing CI environment, I will assume they have a fully automated build with minimal dependencies (chapter 1 and 4). Next, they can use the development team practices from chapter 2 as the cornerstone for moving forward to incorporating other build processes such as database integration (chapter 5), additional automated testing (chapter 6), static/dynamic analysis (chapter 7) and deployment (chapter 8) to a target environment [ August 28, 2007: Message edited by: Paul Duvall ]
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>
Joined: May 06, 2006
For dev teams with an existing CI environment, I will assume they have a fully automated build with minimal dependencies
This is exactly my situation for some mysterious reasons there's always not enough time to add: