1 Welcome
In this chapter:
- Why should you care about Continuous Delivery?
- Understand the history of Continuous Delivery, Continuous Integration, Continuous Deployment and CI/CD
- Define the different kinds of software that you might be delivering and explain how Continuous Delivery applies to them
- Define the elements of Continuous Delivery: Keeping software in a deliverable state at all times and making delivery easy
Hi there! Welcome to my book! I’m so excited that you’ve decided to not only learn about Continuous Delivery, but really understand it. That’s what this book is all about: learning how to make Continuous Delivery really work for you on a day to day basis.
1.1 Do you need Continuous Delivery?
The first thing you might be wondering is if it’s worth your time to learn about Continuous Delivery, and even if it is, is it worth the hassle of applying it you your projects?
The quick answer is YES if the following is true for you:
- You are making software professionally
- More than one person is involved in the project
If both of those are true for you, Continuous Delivery is worth investing in. Even if just one is true, (you’re working on a project for fun with a group of people, or you’re making professional software solo), you won’t regret investing in Continuous Delivery.
“But wait - you didn’t ask what I’m making. What if I’m working on kernel drivers, or firmware, or microservices? Are you sure I need Continuous Delivery?” - You