Continuous Delivery vs Continuous Deployment
If you’ve watched our segment on DevOps and DevSecOps, you’ve heard a lot of terms like Continuous Integration, Continuous Delivery and maybe even Continuous Deployment.
Even though all of them are part of the DevOps process, each has its own requirements, and more importantly, pros and cons.
And understanding these differences is the first step in picking the right approach for your specific use case.
Before getting into Continuous Delivery vs Continuous Deployment, let’s take a step back with Continuous Integration.
CI is the practice where developers merge their changes to the code base in your Git repository, your crown jewel, as often as possible.
These changes are then built, tested and scanned by your CI pipeline which builds and then running automated tests and cybersecurity scans against that build. Tests must include unit, integration, end to end and regression testing! If these tests or scan don’t pass, the changes aren’t merged to your main branch and developers must fix those issues immediately and swarm to ensure the pipeline never breaks.
This enables your teams to shift left and detect cybersecurity and functionality or integration issues faster and prevent you from creating tremendous technology tech that will come back to bite you!
Now, let’s take a look at Continuous Delivery and Continuous Deployment
On this page of the site you can watch the video online Continuous Delivery vs Continuous Deployment with a duration of hours minute second in good quality, which was uploaded by the user In the Nic of Time 14 December 2022, share the link with friends and acquaintances, this video has already been watched 70 times on youtube and it was liked by 1 viewers. Enjoy your viewing!
