Mitch Pronschinske 
Automation: You're Doing it Wrong
Email
The DevOps Zone is
presented by DZone with partners including ThoughtWorks Studios and UrbanCode to bring you the most interesting and
relevant content on the DevOps movement. See today's top DevOps content and be sure to check out ThoughtWorks Studio's Continuous Delivery Whitepapers and UrbanCode's Webinars.
There's a common antipattern in build automation that Eric Minick of UrbanCode described quite well in his blog today:
Eric goes on to say that your strategy here should be to ban developers from logging into the affected server and trying to fix it manually. The first response should instead be to fix the automation to account for the new scenario that's causing the broken build.
You can read the full post here.
A common pattern I see is deployment (or build) automation that routinely fails due to a set of common issues. When the deployment fails, people log into the box they were deploying to, perform the well known fix and get on with their lives. This is a trap that minimizes the value of the automation.
--Eric Minick, UrbanCode
Eric goes on to say that your strategy here should be to ban developers from logging into the affected server and trying to fix it manually. The first response should instead be to fix the automation to account for the new scenario that's causing the broken build.
You can read the full post here.
Tags:
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)
ThoughtWorks Studios and UrbanCode, the sponsors of the DevOps Zone, are champions of the DevOps movement. Their deployment tooling solutions focus on the entire software development lifecycle, involving all parts of an organization, which helps facilitate a migration to the DevOps philosophy.
