Application Lifecycle Approvals Done With or Without Gates
Manual approval processes around software delivery are deeply rooted in the Waterfall approach to Application Lifecycle Management. Including a manual approval as part of a Continuous Delivery Pipeline creates an unnecessary bottleneck. DeployHub allows you to support a ‘gated’ process if it is required, but also offers a better method using an intelligent Calendar.
The Calendar in DeployHub is closely tied to 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.
Reserve a Future Release, or Block a Release From a CI Server When Appropriate
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 lifecycle 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.