Skip to main content

I have read some blog articles, papers and books about Continuous Integration and Continuous Delivery, andbut I still can't find a point where you could say this is where CI ends and CD starts. 

I understand that CI is about integrating code changes by automatically building the new version of the software and testing it as soon as the cahangechange is commitedcommitted. Now some sources say that the code is also being deployed into a production-like environment and automatically tested there as part of CI, while others say the staging and testing in that environment exactly what CD is all about.

So where can you draw the line between Continuous Integration and Continuous Delivery?

I have read some blog articles, papers and books about Continuous Integration and Continuous Delivery, and I still can't find a point where you could say this is where CI ends and CD starts. I understand that CI is about integrating code changes by automatically building the new version of the software and testing it as soon as the cahange is commited. Now some sources say that the code is also being deployed into a production-like environment and automatically tested there as part of CI, while others say the staging and testing in that environment exactly what CD is all about.

So where can you draw the line between Continuous Integration and Continuous Delivery?

I have read some blog articles, papers and books about Continuous Integration and Continuous Delivery, but I still can't find a point where you could say this is where CI ends and CD starts. 

I understand that CI is about integrating code changes by automatically building the new version of the software and testing it as soon as the change is committed. Now some sources say that the code is also being deployed into a production-like environment and automatically tested there as part of CI, while others say the staging and testing in that environment exactly what CD is all about.

So where can you draw the line between Continuous Integration and Continuous Delivery?

Source Link
Josef
  • 387
  • 3
  • 5

Exact gap from Continuous Integration to Continuous Delivery

I have read some blog articles, papers and books about Continuous Integration and Continuous Delivery, and I still can't find a point where you could say this is where CI ends and CD starts. I understand that CI is about integrating code changes by automatically building the new version of the software and testing it as soon as the cahange is commited. Now some sources say that the code is also being deployed into a production-like environment and automatically tested there as part of CI, while others say the staging and testing in that environment exactly what CD is all about.

So where can you draw the line between Continuous Integration and Continuous Delivery?