continuous delivery

Webinar: The Continuous Delivery Feedback Loop - Feb. 22nd 1ET

Register Now

DeployHub Open Source GA March 2017

Learn More

Less Scripting and More Automation delivers a
Mature DevOps Platform

Improve DevOps by driving your Continuous Delivery with Release Management and Build Automation integrated into your Continuous Integration workflow. Incorporating Release Management (also called Application Release Automation), and Build Automation tools into your Continuous Integration provides many benefits beyond what simple scripting can achieve. The ability to see into the readiness of a software release, tracking artifacts, accelerating processes and creating consistency are achieved by the intelligence that automation tools can offer. Below are just a few of the benefits that release management and build automation can bring to Continuous Delivery to drive DevOps to higher levels of maturity and continuous process improvement.

Continuous Delivery Automation Benefits


DevOps Collaboration

Collaborate between Development and Production Operations

Meister for Build Automation and Release Engineer for Release Management align the hand-off of operational tasks between your Development teams and Production Control teams orchestrated by your Continuous Integration server such as Jenkins. By centralizing the steps around building, packaging and deploying software, the Production Control team can easily repeat processes defined by developers for building and deploying software.  By using a community developed knowledge base of continuous integration information related to critical build and release information, diverse teams can stay aligned and in the loop.

Incremental Build and Deploy

Smaller Builds and Releases  with Incremental, and Roll Forward Processing

Get the intelligence you need to manage your builds and releases in smaller, less risky increments, integrated into your agile Continuous Integration practice. Through Meister's source and library dependency management you can perform incremental builds for faster less risky builds. Release Engineer enables incremental deployments using its unique deployment version control approach to determining which Component Versions of an Application requires updating.  Deployment Version Control allows for the jumping forward, "roll forward," or jumping backward "rollbacks," between any two versions, for example between 1.4 to 1.8, including the database updates.

Strategic Software Deployments

Model Driven with a Domain Architecture

Our Continuous Delivery tools are designed for the high-level reuse required by the enterprise supporting multiple languages and platforms. Using a unique model-driven, domain architecture we provide a centralized solution from which to manage, configure, control and report on all elements of the Continuous Delivery process. The domain model enables organizations to securely implement, inherit and reuse any element of Continuous Delivery, including; Packaged Applications, Bespoke Applications, Configurations, Technology Frameworks, Application Containers, Application Components, Artifacts, Third Party Connectivity, Data, Database, Credentials and Actions.

Agentless Software Deployments

Increase Efficiency with Agentless Continuous Delivery 

Release Engineer provides you with a simplified and agentless solution. It prevents you from needing to manage hundreds of remote delivery agents on each end target server which is both costly and error-prone. Release Engineer can be called by Jenkins, eliminating the need to install a Jenkins "slave" on all of your production endpoints (physical or virtual). Agentless deployments eliminate the extra cost and effort associated to an agent-based solution. Release Engineer reduces customers’ operational costs by enabling software deployments to take place without having to rely on agent technology being installed, configured and maintained on every end point within the organization.

Software Build Models and Playbooks

Intelligent, Playbooks and Plug-ins for Low-Level Tasks

Smart control over low-level logic is critical to driving your Continuous Delivery and creating a highly repeatable DevOps process.  Both Release Engineer and Meister provides a model-driven design, using Playbooks and Plug-ins, that standardize build automation and release management activities so your Continuous Integration workflow becomes both highly repeatable and 100% predictable. Your DevOps process is highly dependent upon a consistent Continuous Delivery process. Playbooks and Plug-ins create the standardization that delivers the consistency.

Higher Level DevOps Maturity

Achieve Higher Levels of DevOps Maturity

Our solutions support the use of your existing build and deployment scripts while providing you a road map for achieving a higher level of DevOps maturity through continuous delivery automation. Automation leads to higher levels of DevOps maturity by standardizing Continuous Integration workflows across teams, moving away from one-off scripts to Playbooks and Plug-ins, as well as audit and trend reports that result in continuous process improvement and transparency across the organization.

Accelerated Software Builds

Accelerate Your Builds for faster processing

The compile and link process - referred to as a software "Build" is all to often the bottleneck, particularly in agile environments where the build is executed frequently. Meister's Dynamic Framework allows you to execute builds in parallel reducing build times by as much as 50%.

Continuous Integration at Scale

Continuous Integration at Scale

Executing your Continuous Integration process on a single machine can be slow and inefficient. When your CI process is complex you need to span multiple machines and use machine clusters to determine which machine in the cluster has the most available processing power. Meister's CI Server Pooling can be called by Jenkins, or used directly, either way your Continuous Integration can easily scale.

DevOps and ALM

DevOps for the complete Continuous Delivery Life Cycle

Builds and releases need to be executed across the lifecycle, even when you are working in an agile environment. Seldom is there the case where only one version of the application is used. For example, development is always newer than production. When production breaks, new features should not be included in an emergency fix just because the build can only be done at one life cycle phase. Meister allows you to perform builds and releases that support a life cycle environment, including Emergency builds and fixes. Release Engineer supports the promotion of release 'versions' across the life cycle, staging the version as a release candidate that can be automatically deployed from your Continuous Integration server, scheduled or manually deployed.

Release Calendar Pipeline

Schedules and Calendars

Release Engineer’s Calendar can be utilized to automate your software deployments called from your continuous integration workflow supporting your continuous delivery process. Calendars can also be utilized to block Deployments – this can be especially useful when preventing Production Releases during business hours, or preventing system changes for the duration of a testing window. Your continuous integration server can initiate Release Engineer to execute a software deployment at which time it consults the calendar to determine if the time slot is approved for a deployment. This intelligence allows testers and production control to better manage the frequency of the continuous delivery pipeline.

DevOps reports

DevOps Metrics

Centralized logging, Build Audit, Matching Source to Binary report, Impact Analysis, Trend Analysis, Environment Configuration,  Build Difference Reports, Deployment History and Inventory, Metrics Reports and Graphs are just a few of the reports that our solutions provide. These reports track the progress, time measurement and results of your Continuous Delivery process.

DevOps Workflow Processing

Infrastructure Configuration Management

Release Engineer integrates with infrastructure configuration management tools such as Ansible to include updates to your server environment as part of your Release Management. Not every software deployment is as simple as moving a WAR file out to a server. Some require low level configuration updates, or updates to 3rd party components which is part of the infrastructure configuration management job. Release Engineer bridges both tasks into one logical deployment task.

Promote Builds and Releases

Cross Platform and Multi-language

Meister and Release Engineer were designed to solve the enterprise DevOps challenge. They both support a wide variety of languages and platforms allowing Windows, Linux, z/OS and Unix developers to standardize on a single Continuous Delivery tool set. Release Engineer can deploy to Tandem and iSeries for supporting mid-range systems.

Security and Groups

Administer Users and Groups

Meister and Release Engineer support a security model that allows development teams to manage their particular project and domains, while allowing administrators the ability to secure testing and production environments. The distribution of the administration functions allows developers the control they need, when they need it.


We Support the Tools You Use

  • Cloudfoundry
  • Jenkins Head Center
  • Ansible2017
  • Github
  • Bugzilla
  • Jira
  • Babmoo
  • Chef
  • 1
  • 2
  • 3

Customer Success Stories

  • To improve internal audit, BNSF chose OpenMake Software for build automation, rolling it out to more than 200 users in 30 application teams, Their development environment included Microsoft and Eclipse.

    Read More
  • Meister offers us increased productivity and quality compared to manually controlled builds. Meister also completes the configuration management process through it's central build capabilities allowing Fortis to fully control all internal and external software assets within our fast evolving J2EE world.” --Matthias Pyck, Fortis Bank - Read the case study

    Read More
  • "Release Engineer and Meister provides us an adaptable DevOps platform to manage our software builds and releases across diverse platforms from z/OS to Windows” -- Banorte

  • "UCLA's challenge was to standardize how builds and releases were processed, regardless of the development language used. OpenMake Software provided this across the enterprise." -- University of Southern California , Production Control Team Lead

    Read More
  • 1

A Few of Our Customers

  • Franklin
  • Fis
  • Lm
  • Snl
  • Supervalu
  • Danske
  • Northwestern
  • 1
  • 2

Our Partners

  • CLO Business Partner
  • Smartsol
  • Aptude
  • RH Technology Partner Logo V1 1214clean Cmyk
  • Ca2017
  • Wipro Logo
  • 1