Automation for the people: Continuous Integration anti-patterns, Part 2
Make your life with CI easier by learning what not to do
Anti-patterns delay or prevent the benefits you can experience with Continuous Integration. In the tenth installment of his "Automation for the people" series, and in the second installment of a two-part article, Stelligent CTO, Paul Duvall presents best practices when setting up a CI environment and how to avoid, what he calls, the CI anti-patterns.
Published by the popular IBM developerWorks, the article, "Continuous Integration anti-patterns, Part 2" details five additional anti-patterns that tend to produce adverse effects:
- Bottleneck commits, which typically cause broken builds and frustrated developers
- Continuous Ignorance, a build consisting of minimal automated processes, which results in builds that never
fail
- Scheduled Builds, rather than frequently building software with every code change
- Believing that code Works on My Machine, only to discover problems later in other environments
- Failing to remove old build artifacts, which leads to a Polluted Environment causing false positive and false negative errors
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.
|
