Source: thenewstack.io
CI vs. CD Explained by Emoji: Part 2, Continuous DeliveryCategory: Software, Infrastructure, automation, artificial-intelligence
For Part 2, we’re stretching our CI/CD Pizza (Git)Hut Company analogy as far as it will go and covering continuous delivery (or CD) and how it differs from continuous deployment. Continuous delivery (CD) extends continuous integration from the stage where our stable build 📃 or single artifact has been built and centrally stored, right through to being ready for production.
As you would expect, continuous deployment isn’t suitable for all use cases unless you trust that your AI won’t give you food poisoning — or, worse, approve a salad pizza and deliver that to a customer.
So you can see that when CI and CD are combined, it enables ideas to go from inception to production in a much shorter time frame.
If you want to make pizzas that are better than mamma used to make, CI/CD can help you get there.
As you would expect, continuous deployment isn’t suitable for all use cases unless you trust that your AI won’t give you food poisoning — or, worse, approve a salad pizza and deliver that to a customer.
So you can see that when CI and CD are combined, it enables ideas to go from inception to production in a much shorter time frame.
If you want to make pizzas that are better than mamma used to make, CI/CD can help you get there.
Related Articles
Community Partners
DevOps Careers