What are the benefits of pre-verified and approved application releases?
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 to continuous deployment. As you move into containers and micro-services, the process of manual gates will become a process that is unsustainable. Like standing in line at an airport security gate, deployments will become backed up and the promise of Agile DevOps will not be achieved.
Like getting a ‘TSA Pre-check’, DeployHub solves this problem by allowing testing and production teams to have their release package pre-verified and approved prior to it getting to the security gate. DeployHub allows you to support a ‘gated’ process if it is required, but also offers a better non-stop method with smart calendars for continuous deployment.
The calendar in DeployHub Pro 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 or pre-approved.
Instead of asking for an approval for each continuous 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 or Block a Future Release From a CI Server as Appropriate
The DeployHub Calendar supports continuous deployment by giving you the ability to ‘reserve’ a future date for a release and blocking out times when releases cannot be accepted, 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 for production teams who want to have some control over the Continuous Delivery process related to specific environments across the pipeline.
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 yet ready or available. This feature can be especially useful when preventing Production Releases during business hours, or preventing system changes for the duration of a testing window.
DeployHub’s Key Features
- Blueprint your application’s logical view
- Publish and Catalog Microservices
- Version Microservice Configurations
- Release and Track Microservices
- Manage Database Deployments
- Continuous Deployment Blogs
- Microservice Continuous Integration – Where’s the Build?
- Working with Helm for your Microservices Releases
- Kubernetes Pipeline Challenges and Thougths
- Managing Embedded Configurations
- Questions and Answers on managing a K8s Pipeline
- Running Safe Blue / Green Deployments
- The DeployHub Jenkins Plug-in
- Setting Up the Jenkins Plug-in
- The DeployHub CircleCI Orb
- Creating a Continuous Feedback Loop
- Release Agents – the Enemy of Continuous Deployments
- DeployHubs Release Architecture
- Why we need Application Packages for CD
- Agentless Deployments with DeployHub’s Engine
- Version Jumps and Tracking
- Blogs on Microservice Configuration Management