Continuous Delivery is all about delivering on-demand. But, as we discussed in the differences between release and deployment, delivery, or deployment, it's only the technical part of the Continuous Delivery process. It's all about how you can technically install the software on an environment, but it doesn't say anything about the process that needs to be in place for a release. Release approvals don't control how but control if you want to deliver multiple times a day. Manual approvals also suit a significant need. Organizations that start with Continuous Delivery often lack a certain amount of trust. They don't dare to release without manual approval. After a while, when they find that the approval doesn't add value and the release always succeeds, the manual approval is often replaced by an automatic check. Things to consider when you're setting up a release approval are: What do we want to achieve with the approval? Is it an approval that we need...
Comments
Post a Comment