Continuous Integration vs Continuous Delivery vs Continuous Deployment?
The acronym CI/CD is very famous in the DevOps community and there is a high chance it would come up in any interview for the role of a DevOps engineer. In this article, we will understand the concepts of Continuous Integration, Continuous Delivery, and Continuous Deployment.
Continuous Integration
It focuses on checking the code for errors/quality before it’s merged into your code repository. It lets you ensure the code quality before it is checked into your branch and deployed on any environment. You can configure tests in your pipeline to verify your code and confirm that it would not break your application or other issues that would cause a problem.
Continuous Delivery
Once your code is merged into the repository Continous Delivery lets you deploy it manually via a trigger or action in the deployment pipeline. A weekly sprint where you manually trigger the code deployment on the production system at the end of the sprint would be an example of continuous delivery.
Continuous Deployment
Continuous Deployment takes one step further to deploy all the code automatically to production systems once all the tests have been passed. So, you don’t have any manual triggers or actions to deploy the code to production like in Continuous Delivery. Continuous Delivery speeds up the delivery and feedback loop of the product and helps in a better product development lifecycle.
