Best Practices for Application Release Automation
February 09, 2017

Derek Langone
XebiaLabs

If you're thinking about implementing Application Release Automation (ARA), here are some tips to get started:

Start with: Balancing the Art and Science of Application Release Management

■ Pick one software project and map out all the steps in the release process, from design through production.

■ Take an inventory of the DevOps tools use at each step of the above process.

■ Choose an ARA tool. When researching, look at multiple reference sources, from vendor information, to articles, to analyst reports. Gartner and Forrester both issued 2016 reports that introduce ARA and evaluate key vendors in the space.

■ Look for an ARA solution that, at a minimum, integrates and orchestrates all your existing tools. if you have to manually connect every tool in the pipeline, you won't be able to scale.

■ Besides implementing a good CI solution to automate your application builds, pick some areas in your release process to automate right away. For example, if you have to update your ticketing system to denote that an application has been deployed to a staging environment, integrate your ARA tool to automatically update the ticket with the appropriate deployment information.

■ Train everyone involved in the release process (including non-technical people) on how to use the ARA tool, so each person understands how they can do their job in the release process.

■ Optimizing your release process is like paying back a lot of credit cards: find your biggest bottlenecks and remove them first.

■ Determine some key KPIs by which to measure success, such as time to delivery, deployment frequency, change volume, success rate and mean time to recovery.

Only after a single team gets its first ARA project off the ground and running in production, should you start rolling out the new process and the ARA solution to other teams. To encourage widespread adoption, it's important to show others in the organization that the team was able to achieve its core success metrics.

Derek Langone is CEO of XebiaLabs.

Derek Langone is CEO of XebiaLabs

The Latest

August 16, 2018

There once was a time in software development where developers could design, build and then think about their software's security. However in today's highly connected, API-driven application environment, this approach is simply too risky as it exposes the software to vulnerabilities ...

August 15, 2018

Microservices are a hot topic in IT circles these days. The idea of a modular approach to system building – where you have numerous, smaller software services that talk to each other instead of monolithic components – has many benefits ...

August 13, 2018

Agile is expanding within the enterprise. Agile adoption is growing within organizations, both more broadly and deeply, according to the 12th annual State of Agile report from CollabNet VersionOne. A higher percentage of respondents this year report that "all or almost all" of their teams are agile, and that agile principles and practices are being adopted at higher levels in the organization ...

August 09, 2018

For the past 13 years, the Ponemon Institute has examined the cost associated with data breaches of less than 100,000 records, finding that the costs have steadily risen over the course of the study. The average cost of a data breach was $3.86 million in the 2018 study, compared to $3.50 million in 2014 – representing nearly 10 percent net increase over the past 5 years of the study ...

August 08, 2018

Hidden costs in data breaches – such as lost business, negative impact on reputation and employee time spent on recovery – are difficult and expensive to manage, according to the 2018 Cost of a Data Breach Study, sponsored by IBM Security and conducted by Ponemon Institute. The study found that the average cost of a data breach globally is $3.86 million ...

August 06, 2018

The previous chapter in this WhiteHat Security series discussed dependencies as the second step of the Twelve-Factor App. This next chapter examines the security component of step three of the Twelve-Factor methodology — storing configurations within the environment.

August 02, 2018

Results from new Forrester Consulting research reveal the 20 most important Agile and DevOps quality metrics that separate DevOps/Agile experts from their less advanced peers ...

July 31, 2018

Even organizations that understand the importance of cybersecurity in theory often stumble when it comes to marrying security initiatives with their development and operations processes. Most businesses agree that everyone should be responsible for security, but this principle is not being upheld on a day-to-day basis in many organizations. That’s bad news for everyone. Here are some best practices for implementing SecOps ...

July 30, 2018

While the technologies, processes, and cultural shifts of DevOps have improved the ability of software teams to deliver reliable work rapidly and effectively, security has not been a focal point in the transformation of cloud IT infrastructure. SecOps is a methodology that seeks to address this by operationalizing and hardening security throughout the software lifecycle ...

July 26, 2018

Organizations are shifting away from traditional, monolithic architectures, with three-quarters of survey respondents delivering at least some of their applications and more than one-third delivering most of their applications as microservices, according to the State of DevOps Observability Report from Scalyr ...

Share this