Coding With Fun
Home Docker Django Node.js Articles Python pip guide FAQ Policy

What is the difference between continuous integration and continuous delivery?


Asked by Harlow Barajas on Dec 01, 2021 FAQ



In order to do Continuous Deployment you must be doing Continuous Delivery. Continuous Integration usually refers to integrating, building, and testing code within the development environment. Continuous Delivery builds on this, dealing with the final stages required for production deployment.
Thereof,
To put it simply continuous integration is part of both continuous delivery and continuous deployment. And continuous deployment is like continuous delivery, except that releases happen automatically. What are the benefits of each practice?
Indeed, The CI/CD pipeline begins with the process of Continuous Integration. The process of Continuous Integration allows the developers to integrate code changes into a shared repository continuously. The code in this process is continually tested and incorporated more smoothly. After the Integration phase, comes the Continuous Delivery phase.
In this manner,
With CI, they are all independently able to push their code continuously into a branch in a shared Github repo. As they work, code can be tested (and iterated on) using a Jenkins server. Continuous Delivery goes beyond CI because it refers to how code is tested, staged, and deployed.
Similarly,
Continuous Delivery is described as the logical evolution of continuous integration: Always be able to put a product into production! Continuous Deployment is described as the logical next step after continuous delivery: Automatically deploy the product into production whenever it passes QA!