Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; plgSystemAddCustomCSS has a deprecated constructor in /home/openmake/public_html/plugins/system/addcustomcss/addcustomcss.php on line 18
Pipeline Calendar

Our Competitive Difference

Contact Us for More Information at 505.424.6439 or

Email Us

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. DeployHub allows you to support a 'manual' process if it is required, but also offers a better method using an intelligent Calendar. The Calendar in DeployHub is closely tied to continuous delivery pipeline calendar each 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 DeployHub 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.

DeployHub’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.

Our Competitive Difference

Stack Management & Audit

  • 1

OSS Vs. Pro

ARA Features
Open Source
Pro
Easy Installation - No End Point Agents  Checkmark Sm Checkmark Sm
Easy to configure - graphical application packaging  Checkmark Sm Checkmark Sm
Release Train Management (manage multiple applications) Checkmark Sm Checkmark Sm
Calendar with integrated pre-approvals and blocking Checkmark Sm Checkmark Sm
Role Based Security Checkmark Sm Checkmark Sm
Change Request Tracking Checkmark Sm Checkmark Sm
Continuous Feedback Loop from issue tracking to endpoint  Checkmark Sm Checkmark Sm
Change Request Burn Down Charts Checkmark Sm Checkmark Sm
Component Sharing and Workflow Templates Checkmark Sm Checkmark Sm
Integrates with Infrastructure Configuration Management Checkmark Sm Checkmark Sm
Push or Pull deployments with version 'jumping' Checkmark Sm Checkmark Sm
Database Management Support Checkmark Sm Checkmark Sm
Pre-Built Reusable Deployment Actions and Workflows Checkmark Sm Checkmark Sm
Jenkins and Continuous Delivery Plugins Checkmark Sm Checkmark Sm
Multi-Platform (Linux, UNIX, Windows, z/OS, iSeries, Cisco Routers) Checkmark Sm Checkmark Sm
Rollback and Roll Forward Recovery Checkmark Sm Checkmark Sm
Environment Modeling and Management Checkmark Sm Checkmark Sm
Continuous Feedback Loop from Build to End Point Checkmark Sm Checkmark Sm