Automation for the people: Continuous Integration anti-patterns
Make your life with CI easier by learning what not to do
In the ninth installment of his "Automation for the people" series, Stelligent CTO, Paul Duvall, shows you how to make the most from the practice of Continuous Integration by learning what not to do.
Published by the popular IBM developerWorks, the article, "Continuous Integration anti-patterns" details six common anti-patterns and, most importantly, how to avoid them:
- Infrequent check-ins, which lead to delayed integrations
- Broken builds, which prevent teams from moving on to other tasks
- Minimal feedback, which prevents action from occurring
- Receiving spam feedback, which causes people to ignore messages
- Possessing a slow machine, which delays feedback
- Relying on a bloated build, which reduces rapid feedback
The "Automation for the people" series is dedicated to exploring the practical uses of automating software development processes and teaching you when and how to apply automation successfully. Also, check out developerWorks' "Improve Your Java Code Quality" discussion forum for topics addressing best practices for ensuring your code is the best it can be.
|
