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


Polarion SVN Importer

Using the Polarion SVN Importer tool Lessons on Polarion SVN Importer On and off over the last few years or so I have been working with the open-source Polarion SVN Importer tool to help customers migrate to Subversion Read more...


Debugging Microservices

I am in the process of moving DeployHub Pro to microservices for our SaS offering and I ran into an interesting dilemma. Microservices are great for having small contained pieces of functionality for scalability and Read more...


Why is Docker so Ubuntu-centric?

Docker and Ubuntu tight integration It seems that Ubuntu is the OS of choice for Docker users. Here at OpenMake Software we have started down the path to integrating Docker into our products and our Read more...