Skip to content

Latest commit

 

History

History
13 lines (7 loc) · 1.04 KB

04.1_cd-overview.md

File metadata and controls

13 lines (7 loc) · 1.04 KB

CD From 30,000ft ✈️ {docsify-ignore-all}

As we just learned, CI is the ability to quickly integrate many changes to a mainline and is often accompanied by some form of automated testing. The final step in a good CI pipeline is producing some sort of artifact, usually an application, that is ready to be packaged for some deployment.

This is where CD enters the scene

The practice of taking that artifact and ensuring it is fully packaged and delivered to a pre-production environment is Continuous Delivery.

CD allows get's your application to be "one click" deployed on whatever release schedule your project needs require. With that said, the benefits of CD are better realized if you get your changes into production as soon as possible.

But I want to deploy!

As most of you know the next phase in any DevOps related pipeline is that of Continuous Deployment, which is the removed of that automated "one click" process in favor of an automated release process that places your changes into production without the need for humans!