Join the DZone community and get the full member experience.
Join For Free
The DevOps Zone is brought to you in partnership with Sonatype Nexus. The Nexus Suite helps scale your DevOps delivery with continuous component intelligence integrated into development tools, including Eclipse, IntelliJ, Jenkins, Bamboo, SonarQube and more. Schedule a demo today.
There's a common antipattern in build automation that Eric Minick of UrbanCode described quite well in his blog today:
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
The DevOps Zone is brought to you in partnership with Sonatype Nexus. Use the Nexus Suite to automate your software supply chain and ensure you're using the highest quality open source components at every step of the development lifecycle. Get Nexus today.
Opinions expressed by DZone contributors are their own.