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 includes all of the artifacts to be delivered and where they should be referenced. Release Engineer clarifies this process and provides a IDE for defining the data which includes repositories (where the file lives), components(release artifacts), application (collection of components) and releases (collection of applications).  Our competitors such as IBM UDeploy does not manage up to a release level. For this you must purchase URelease.  When we designed Release Engineer we considered what the enterprise would need, and managing multiple releases was seen as a critical feature.

In Release Engineer, Applications package together components and Releases package together Applications.  This packaging enables you to release multiple applications together out to an environment.  Applications dependencies are at a higher level than component to component dependencies.  These dependencies are usually driven by changes in data structures, communication layers or by reusable components.


software release packaging

Repository and Components

Everyone get up and move over…

Lets say that you have a reusable logging routine that has changed (backward compatibility broken) and multiple applications consume the reusable logging routine from a shared area.  Each application should be re-released using the new logging routine.  Release packaging in Release Engineer enables you to create a release with all of the applications that use the reusable logging component and then deploy the whole release to an environment, instead of deploying each application individually.  Also, the release packaging shows at a quick glance which applications are going to be deployed.  Everything is transparent so applications are not missed.

Taking this level of release packing out of the shadows of a manifest files, and into the light using a graphical mapping tool clarifies how your components, applications and releases fit together.


Steve Taylor

CITA OpenMake Software

0 thoughts on “Release Packaging for Release Management”

Leave a Reply

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

Related Posts


Which one is better, Kubernetes or Netflix Eureka?

I have been doing some research on the differences between Netflix’s Eureka and Kubernetes. The main difference that I have found is that Eureka is focused on micro-services from the coding level. You write your Read more...


Deployment Version Control for Release Management and Continuous Delivery

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 Read more...


Moving from Ant to Meister – No conversion required

Ant to Meister conversion is not required Don’t believe that an Ant to Meister conversion is needed to move to Meister Build services Our competitors would like you to believe that an Ant to Meister Read more...