Release Management, cornerstone of Continuous Delivery

Deployment Version Control, Critical Release Management feature for Continuous Delivery

Release Management is best achieved when the Continuous Delivery process relies on an application release automation (ARA) solution that supports deployment version control.  Release Engineer has the intelligence to sort out the incremental change between ANY two releases – not just between 1.1 to 1.2 for example.  Deployment version control, like software version control, tracks the incremental changes between each delta. Release Engineer uses a relational database to forward chain the deltas for each software deployment, including database alters.  When a deployment occurs, Release Engineer updates the database to capture the delta.  Deployment Version Control makes rolling back, rolling forward or Jumping Versions fast and easy.
Jumping your software deployment forward or backward at any time is an essential feature in Release Management. In is what allows the integration of database and infrastructure configuration management steps into the deployment process. Without it, the release management tool is simply allowing you to update files without the intelligence of the supporting environment.

Release Engineer handles the management of continuous delivery using both Roll-Forward and Rollback technology based on each component of your Application.  Rollback is a standard feature of deployments that allows the entire application to be returned to the previous state. Release Engineer takes this concept a step further using Roll-Forward. Roll-Forward allows you to execute a deploy that automatically upgrades all targets to a single ‘specified’ release. This includes the ability to jump across multiple versions and handle all of the in between deployment steps. For example, testing might not accept every release from the development team. This can cause testing to be several releases behind. Release Engineer allows testing to move from 1.1 to 2.0 and deals with all of the incremental steps, including the database. No additional work needed. Jumping back is just as easy in the case that Production wants to rollback from 2.0 to 1.0.
Software Deployment version control supports rollback and roll forward processing.

Roll Forward/Roll Back Software Deployments

Release Engineer manages the incremental change at the database level and the application-level, making it one of the only software deployment products on the market that can effectively manage incremental updates of multi-tiered applications. Incremental processing of your continuous deployment minimizes the need for performing monolithic deployments and instead supports agile, continuous delivery where changes are moved “forward” or “backwards” on an as needed basis.
Release management with deployment version control

Incremental Updates


Ms. Ragan has had extensive experience in the development and implementation of DevOps for large organizations. She began her consulting career in 1989 on Wall Street specializing in build, testing and release management for the distributed platform. It was during her consulting experiences that Ms. Ragan recognized the lack of standardized development procedures on open systems that were common on the mainframe. In the years leading to the creation of OpenMake Software she worked with development teams in implementing a community driven standardized build and deploy process that enabled frequent builds and releases, automated around version control. Her knowledge and experience contributed to the creation of OpenMake Meister, the first commercial Build Automation solution. Ms. Ragan served on the Eclipse Foundation Board of Directors as an Add-in Provider Representative for 5 years. She has been published on numerous occasions and regularly speaks at conferences including CA World where she presented for 15 consecutive years. She holds a BS Degree in Business Administration, Computer Technology from California State University, Pomona.

0 thoughts on “Deployment Version Control for Release Management and Continuous Delivery”

Leave a Reply

Your email address will not be published. Required fields are marked *

Related Posts


Release Packaging for Release Management

Release Packaging to Improve Software Deployments Release Packaging a requirement for Release Management Release packaging for release management is done in a graphical method with Release Engineer.  Other solutions uses a hard-coded manifest file that Read more...


wsadmin get list of servers in a cluster

WSAdmin used in headless mode by Release Engineer Use WSAdmin with Release Engineer to manage server clusters This blog covers how to get a list of servers in a cluster using wsadmin.  Managing a cluster Read more...


Application Release Automation integrated with IT Engines such as Chef, Puppet and Ansible

Companies shopping for Application Release Automation solutions often confuse the functionality of IT Engines such as Ansible, Chef and Puppet as potential tools to address the ARA challenge. IT Automation engines are designed to automate Read more...