When your application is ready, you need to make it available to users. This is called deployment. You could do this manually: upload files, run commands on a server, or click buttons in a dashboard. But what happens when you push code every day? Or when multiple people on your team push code? Doing everything manually becomes slow and error-prone. Continuous Delivery solves part of this by automating everything up to deployment. Every time code is pushed and passes all checks (like tests, build), it is automatically packaged and ready to go live. A human then decides when to deploy, usually by clicking a button or approving a release.
Continuous Delivery builds on top of CI. Where CI verifies your code (lint, test, build), CD takes the verified result and makes it ready to ship. Together they form one automated pipeline: push → verify → ready to deploy.
https://www.youtube.com/watch?v=2TTU5BB-k9U
Key takeaway from the video:
Continuous Delivery builds on top of CI. Where CI verifies your code (lint, test, build), CD takes the verified result and makes it ready to ship. Together they form one automated pipeline: push → verify → ready to deploy.
<aside> 💭
Every development team has its own CD process. It depends on the team, product, company, and other factors.
</aside>
The HackYourFuture curriculum is licensed under CC BY-NC-SA 4.0 *https://hackyourfuture.net/*
Built with ❤️ by the HackYourFuture community · Thank you, contributors
Found a mistake or have a suggestion? Let us know in the feedback form.