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

What is the difference between continuous integration and continuous deployment?


Asked by Emani Wu on Dec 01, 2021 FAQ



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.
In respect to this,
Although the terms are often used interchangeably, most people are referring to Continuous Delivery when they refer to CD. That’s simply because Continuous Delivery came into prominence slightly earlier than Continuous Deployment. They may have the same prefix, but these processes have some pretty clear differences.
Just so, If you answered no to any, you may need to start with continuous integration and continuous delivery (CI/CD). You will automate the creation of production-ready code that is always just one manual approval from deployment.
Besides,
Continuous integration/ continuous builds is all about getting developers to commit code to a source code repository little and often (and get the latest version from the repository, so any further changes are based on other developers recent changes). This reduces the time wasted on merge resolution, as it's easier to merge in this case.
Next,
Continuous Deployment is a step up from Continuous Delivery in which every change in the source code is deployed to production automatically, without explicit approval from a developer. A developer’s job typically ends at reviewing a pull request from a teammate and merging it to the master branch.