
Where do Continuous Delivery and Continuous Integration come from?
Where do Continuous Delivery and Continuous Integration come from?
This post explores the different deployment strategies and practices to help you succeed with your production deployments.
Introducing the Events SIG: a vendor-neutral, open effort to drive the standardization and interoperability between Continuous Delivery systems through events.
Jenkins is a great CI solution, and Spinnaker is a great CD solution. While it’s possible to get along without one of them, it’s simpler to use both.
Don’t miss the Continuous Delivery talks at FOSDEM. No registration necessary!
The pace of digitization is unlikely to slow down and many of the 2020 changes are here to stay. Read about some of the trends that will define 2021.
I recently enjoyed reading Anton Weiss’ post “Let’s stop fooling ourselves. What we call CI/CD is actually only CI.” and it seemed to resonate with many of you too.
Explore the origins of continuous delivery, how it has evolved and where it is going.
CI, CD/D and DevOps methodologies are crucial to ensuring relevance, profitability, and fast innovation. However, the domain’s lack of interoperability and common standards make this challenging. What are those challenges and how can we work together to address them?
At the end of September, I wrote a blog called “We Need to Stop Using the Term CI/CD,” not to destroy something that you’re used to, but because I believe that CI/CD is a confusing and misleading term.