Skip to main content

Release approvals

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 for compliance reasons? 
  • Who needs to approve? We need to know who needs to approve the release. Is it a product owner, Security officer, or just someone that isn't the one that wrote the code? It's essential because the approver is part of the process. They're the ones that can delay the process if not available. So be aware of it.
  • When do you want to approve? Another essential thing to consider is when to approve. It's a direct relationship with what happens after approval. Can you continue without approval? Or is everything on hold until approval is given. By using scheduled deployments, you can separate approval from deployment.

Although manual approval is a great mechanism to control the release, it isn't always helpful. Scheduled deployments have already solved the dependency issue.

You don't have to wait for a person in the middle of the night. But there's still a manual action involved.


 

Navigation


Labels:

Comments

Post a Comment

Popular posts from this blog

What is release, and what is a deployment?

T o understand the concepts and the technical implementation in many tools, you need to know how tool vendors define the difference between a release and a deployment. A  release  is a package or container containing a versioned set of artifacts specified in a release pipeline in your CI/CD process. It also includes a snapshot of all the information required to carry out all the tasks and activities in a release pipeline, such as: The stages or environments. The tasks for each one. The values of task parameters and variables. The release policies such as triggers, approvers, and release queuing options. On the other hand,  Deployment  is the action of running the tasks for one stage, which results in a tested and deployed application and other activities specified for that stage. Starting a release starts each deployment based on the settings and policies defined in the original release pipeline. There can be multiple deployments of each release, even for one stage. ...
Post a Comment
Read more

DevOps - What and Why?

The very first question arises in the mind is " What is DevOps? " Few will say it combined team of Developers and Operations. Some will say it is a person "DevOps Engineer" who works with multiple teams to get the things done in corrective manner. Further questions comes in mind are: What is the corrective manner of doing things? How it is different from our "current" method of doing things? Do I need an extra set of tools for this? And, most important of them all, why should I use it? Let me tell you what I've learn in my 3 days of DevOps training. What is DevOps? DevOps is not a team, or tool, DevOps is a culture. It is a culture for collaboration, Integration and Communication between different cross functional teams for  Continuous Delivery . DevOps is not an additional team, but it is the existing team members who work together. It breaks the barrier between Infrastructure and Code at early stage. DevOps also encoura...
1 comment
Read more

Adding JQuery to Blogger

  JQuery is the now a day very famous and came in 8 out of 10 webpages we visit. There is nothing dificult yo add this to your own blog. All you have to do is to add one line of code (script) to your blog's template’s header. <script src="http://ajax.googleapis.com/ajax/libs/jquery/1.2.6/jquery.min.js" type="text/javascript"></script> FYI: You don't need to upload any file or anything. Google will host it for your. STEPs to add jQuery to Blogger: Login to your dashboard; Choose your blog; From the top menu select “Layout”; Then select “Edit HTML” sub-menu; Add the above code anywhere between <head></head> tag (or alternatively, just above </head> tag) and you are done. Now, you can add jQuery plugins to your blog. Enjoy coding.... ;)
Post a Comment
Read more