DZone
DevOps Zone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
  • Refcardz
  • Trend Reports
  • Webinars
  • Zones
  • |
    • Agile
    • AI
    • Big Data
    • Cloud
    • Database
    • DevOps
    • Integration
    • IoT
    • Java
    • Microservices
    • Open Source
    • Performance
    • Security
    • Web Dev
DZone > DevOps Zone > Go Forth... and Automate!

Go Forth... and Automate!

Sam Fell user avatar by
Sam Fell
·
Feb. 26, 15 · DevOps Zone · Interview
Like (0)
Save
Tweet
4.85K Views

Join the DZone community and get the full member experience.

Join For Free

Application Release Automation, or ARA, is the consistent, repeatable and auditable process of packaging and deploying an application or update of an application from development, across various environments, and ultimately to production.

“Go forth…and automate!” says Wesley Pullen, general manager and vice president of deployment solutions at Electric Cloud. He declares this in his recent article on DevOps.com. hy such a declaration? Because software organizations that implement successful ARA eliminate the need to build and maintain custom scripts for application deployments, while simultaneously reducing configuration errors and downtime. In other words, by automating the release process, software organizations can deploy better software faster.

So how does an organization implement Application Release Automation? Wesley points out in the article that there are five fundamental building blocks of successful ARA:

  1. Packaging – Packaging creates the bill of materials for your deployment. It is your way of knowing exactly what you need to move from point A to point B.
  1. Dependencies - Dependencies are a critical cog in the ARA process. When you are working on your release, you need to understand what other applications or components are involved for its success.
  1. Promotion – Promotion in the context of Application Release Automation is the process of moving the application or update from one stakeholder to the next so that the release is as close to perfect as possible before it is deployed.
  1. Deployment – Deployment is the act of launching your application and from point A to point B. Using the word “launch” is no mistake – it’s just like the commander of a space operation pushing the launch key.
  1. Compliance – Compliance is literally, “Are you following the rules of the game?” However, the rules of compliance vary wildly within different environments.

With a strong understanding of these five building blocks, you will have a solid base to start exploring the wonderful world of Application Release Automation. Click here to check out Wesley’s article to learn more and, “Go forth…and automate!”


application

Published at DZone with permission of Sam Fell, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • The Engineer’s Guide to Creating a Technical Debt Proposal
  • SDLC Vs STLC: What's the Difference?
  • How To Integrate Third-Party Login Systems in Your Web App Using OAuth 2.0
  • Application Scalability — How To Do Efficient Scaling

Comments

DevOps Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • MVB Program
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends:

DZone.com is powered by 

AnswerHub logo