ARA Features Unique to Release Engineer

Always Approved Continuous Delivery Pipelines

Continuous Delivery that is Approved - Until it is Not

 
Manual approval processes around software delivery are deeply rooted in the Waterfall approach to Application Life Cycle Management. Including a manual approval as part of a Continuous Delivery Pipeline creates an unnecessary bottleneck. Release Engineer allows you to support a 'manual' process if it is required, but also offers a better method using an intelligent Calendar. The Calendar in Release Engineer is closely tied to continuous delivery pipeline calendareach Environment where software is to be installed. Users who own the Environment control the Calendar and can define time slots when a Continuous Delivery Deployment should be rejected. Instead of asking for an approval for each CD deployment, the calendar is used to indicate when the Environment is 'open' for business, or 'closed' to accepting a new release. This method avoids the need to request an approval every time a Continuous Delivery process needs to deploy new features.

The Release Engineer Calendar supports the concept of 'reserving' a future date for a release and blocking out times when releases cannot be excepted, such as during a maintenance window. When a software deployment is triggered from a CI server such as Jenkins, the Calendar is referenced to determine if the Environment will accept the release, or if the release must be 'reserved.' This calendaring intelligence is particularly useful to testing and production teams who want to have some control over the Continuous Delivery process related to specific life cycle environments.

Release Engineer’s calendar is built into the software deployment logic. Scheduling functionality can be utilized to automate an ‘off hours’ deployment, or to block a deployment from being initiated by a CI server because the environment is not ready or available. This calendaring feature can be especially useful when preventing Production Releases during business hours, or preventing system changes for the duration of a testing window.

Enterprise Platform support

Release Engineer runs on a Linux or Windows server, includes a web based UI and supports software deployments to multiple platforms and can support a deployments that include cross platforms. It also supports WebSphere Deployments, database deployments and integrates with external repositories for retrieving binaries.

Platform Support Includes:

Windows 2008, Windows 2012
Solaris, HP-UX, AIX, Linux
Ubantu, Redhat, SuSe, Debian
Tandem, Stratus, IBM iSeries, OpenVMS, Unisys, IBM 4690
z/OS
IBM WebSphere
Jetty, Tomcat, Cloud Foundry
Microsoft IIS
Microsoft SQL Server
Oracle
Sybase