He effectively IS a teacher. He may not be handing out tests or caring about attendance, but he is one of the greatest educators I've come across. I started a DevOps internship at the start of the month and his videos have been a huge help for when documentation and articles start to bleed together and become incomprehensible.
Thanks - excellent video and really simple and easy to understand explanation of Continuous Deployment vs Continuous Delivery. Have always seen that process where you have to do a gate review (eyes wide open) to get a decision and a thumbs up to do the final bit and deliver.
Thank you have explained it really well. To confirm continuous deployment is completely automated versus in continuous process the last step is where human intervention is done?
Right, that continuous deployment is typically fully automated to prod. Most people talking about "continuous delivery" imply some degree of human interaction - usually towards the end of the process.
If you have a threshold set of "100% of the tests should pass", then what would be the point of the human intervention of go, no-go decisions? And vice versa if the threshold is set less than 100%, then how would continuous deployment be trustworthy?
Thank you so much for this question, otherwise I would have thought I‘m the only one who asks this question. Unfortunately, I don‘t have an answer. Does anybody else can answer it please?
Driving humans out of release decision-making is a good and noble goal. The 100% test passing assumes that tests are comprehensive enough that they can be trusted. Do the tests cover functionality, performance, security and useability concerns sufficiently? For many, that's not the case. It also assumes that the deploy/release mechanics are not inherently risky. Can the retailer safely release changes on Black Friday or should an executive make a risk/reward decision? Even once the technology is in place, many organizations have policies that require some sort of approval. "The auditors say we have to have it" kind of stuff.
Hi, great video! Quick question. What would be the use of having a Staging Server if Continuous deployment is used? I mean the staging server is to check if your development works well so if it's going to pass directly from Staging to Production in contiuous deployment, what would be the use of it ? I mean in Continuous delivery makes totally sense, so I hope someone could explain, thanks
A deployment just to test the deployment probably isn't needed. Using a production like environment for automated tests and using the deployment to that test environment as part of testing your deployment? That makes sense.
With Q\A is meant a unit testing ? Or some other testing. When we do build we also run all unit test. Without successful passing of unit test is not build ?
QA in this example is a placeholder for early environments where some sort of run-time testing is done (as opposed to code-level unit tests). An environment where the software is installed and exercised. For most teams I've worked with there are 1-5 environments/namespaces/places that the two QA and Stage environments represent here.
Very good debate. I totally understand now when in the insurance/banking domain are so afraid of the "prod-deployment".. its funny cos as you pointed rather build the automation to rollback and leverage the QA as a IT joke "Chuck Norris tests in production" ;-D
Does organizations following Continuous Deployment have SOCII certification? I am asking because I ve experienced an auditor specifically asking for deployment approvals into production. Seems strange to me.
I don't know enough of the details of SOC 2, however... You might check out IT Rev's "DevOps Audit Defense Tool Kit" (itrevolution.com/devops-audit-defense-toolkit/). Generally, you need some sort of controls around what goes into production for most certifications. So what you want to show is that every change is reviewed (often a code review) and good efforts are put in place to govern change. So where the auditor might look for an approval from the QA Management on quality in a traditional environment, in a CD environment, you show that appropriate leaders approved test coverage and test success benchmarks and that each build going into production has a record of having cleared those benchmarks. You show that you've automated what used to be manual controls. Given SOC 2's emphasis on security, I think that second pair of eyes on every change (fraud requires conspiracy, not a single actor) and evidence of security testing would have a good chance. I always encourage talking to auditors before the audit.
Eric, all your videos are awesome. You keep it so simple. You would make a great teacher. Thanks a ton.
he IS a teacher
He effectively IS a teacher. He may not be handing out tests or caring about attendance, but he is one of the greatest educators I've come across. I started a DevOps internship at the start of the month and his videos have been a huge help for when documentation and articles start to bleed together and become incomprehensible.
@@JoshuaDWeinstein Thank you! This is one of the nicest things someone has said about me in my career. This whole thread is so sweet.
Thanks - excellent video and really simple and easy to understand explanation of Continuous Deployment vs Continuous Delivery. Have always seen that process where you have to do a gate review (eyes wide open) to get a decision and a thumbs up to do the final bit and deliver.
Such an easy to understand video thanks so much
Really helped me understand the difference, thanks! :)
Thank you have explained it really well. To confirm continuous deployment is completely automated versus in continuous process the last step is where human intervention is done?
Right, that continuous deployment is typically fully automated to prod. Most people talking about "continuous delivery" imply some degree of human interaction - usually towards the end of the process.
@@ericminick1700 Thanks for that, I know it's a question from someone else but it helped me out. :)
@@ericminick1700 is it still continuous delivery if there is still some manual testing that cannot be automated?
Thanks so much for this tutorial.
If you have a threshold set of "100% of the tests should pass", then what would be the point of the human intervention of go, no-go decisions? And vice versa if the threshold is set less than 100%, then how would continuous deployment be trustworthy?
Thank you so much for this question, otherwise I would have thought I‘m the only one who asks this question. Unfortunately, I don‘t have an answer. Does anybody else can answer it please?
@@DarkFurios the point is some big guy must handle the weight of the responsibility (if something goes wrong, they must answer)
Driving humans out of release decision-making is a good and noble goal. The 100% test passing assumes that tests are comprehensive enough that they can be trusted. Do the tests cover functionality, performance, security and useability concerns sufficiently? For many, that's not the case.
It also assumes that the deploy/release mechanics are not inherently risky. Can the retailer safely release changes on Black Friday or should an executive make a risk/reward decision?
Even once the technology is in place, many organizations have policies that require some sort of approval. "The auditors say we have to have it" kind of stuff.
thank you simple and crisp
Thank you for watching! 👍
Hi, great video! Quick question. What would be the use of having a Staging Server if Continuous deployment is used? I mean the staging server is to check if your development works well so if it's going to pass directly from Staging to Production in contiuous deployment, what would be the use of it ? I mean in Continuous delivery makes totally sense, so I hope someone could explain, thanks
A deployment just to test the deployment probably isn't needed. Using a production like environment for automated tests and using the deployment to that test environment as part of testing your deployment? That makes sense.
Rock on! Nice video. Thx!
Glad you like it!
thanks
With Q\A is meant a unit testing ? Or some other testing. When we do build we also run all unit test. Without successful passing of unit test is not build ?
QA in this example is a placeholder for early environments where some sort of run-time testing is done (as opposed to code-level unit tests). An environment where the software is installed and exercised. For most teams I've worked with there are 1-5 environments/namespaces/places that the two QA and Stage environments represent here.
amazing video, thanks!
Great video
informative thanks
Excellent video!!!
Very good debate. I totally understand now when in the insurance/banking domain are so afraid of the "prod-deployment".. its funny cos as you pointed rather build the automation to rollback and leverage the QA as a IT joke "Chuck Norris tests in production" ;-D
Does organizations following Continuous Deployment have SOCII certification? I am asking because I ve experienced an auditor specifically asking for deployment approvals into production.
Seems strange to me.
I don't know enough of the details of SOC 2, however...
You might check out IT Rev's "DevOps Audit Defense Tool Kit" (itrevolution.com/devops-audit-defense-toolkit/).
Generally, you need some sort of controls around what goes into production for most certifications. So what you want to show is that every change is reviewed (often a code review) and good efforts are put in place to govern change. So where the auditor might look for an approval from the QA Management on quality in a traditional environment, in a CD environment, you show that appropriate leaders approved test coverage and test success benchmarks and that each build going into production has a record of having cleared those benchmarks. You show that you've automated what used to be manual controls.
Given SOC 2's emphasis on security, I think that second pair of eyes on every change (fraud requires conspiracy, not a single actor) and evidence of security testing would have a good chance. I always encourage talking to auditors before the audit.
now i get it, big thnx 🔥
Awesome ! Thank you !
One question: what exactly is meant by "production". Is it simply referring to deploying the code to where the end-user can actually access it?
Where end-users do actually use it. For real.
Was everything written backwards?
Nah - reversed the image in editing.
Make on kubernetes
Hi there Rajan! Here's our playlist of videos on Kubernetes essentials ➡️ ibm.co/3HJhCud
🙂