Automation for the people, Continuous Integration anti-patterns, Part 2

Make your life with CI easier by learning what not to do

From the developerWorks archives

Paul Duvall

Date archived: December 19, 2016 | First published: March 04, 2008

While Continuous Integration (CI) can be extremely effective at reducing risks on a project, it requires a greater emphasis on your day-to-day coding activities. In this second installment of a two-part article on CI anti-patterns, automation expert and co-author of Continuous Integration: Improving Software Quality and Reducing Risk, Paul Duvall, continues laying out CI anti-patterns, and more importantly, demonstrates how to avoid them.

This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.

Zone=Java development
ArticleTitle=Automation for the people: Continuous Integration anti-patterns, Part 2