CD in the Real World
It’s true, some people still think CD is just tools. Here are some reports from people who are on the journey to migrate to a CD flow.
- Josh Warden on learning how to implement trunk-based development
- Experience report from a Walmart development team in 2017
- Edward Thomson on trunk-based development at Microsoft
- Rachel Potvin on trunk-based development at Google
- Claire Liguori on trunk-based development at Amazon
- Ken Mugrage on trunk-based development as part of modern Continuous Delivery
- Jez Humble on the three-year-long transition to CI/trunk-based development in the HP LaserJet firmware team
- John Allspaw and Paul Hammond on trunk-based development with feature toggles at Flickr (in 2009)
MinimumCD is a fantastic way to get to the meat of CD quickly. It’s a clear, focused, no-holds-barred statement of what it takes to achieve CD. This matters because CD works, and it works better than any other way of delivering software that anyone has found so far.
If you aren’t practicing CD in the way that MinimumCD describes it, then you are building worse software more slowly. The trouble is, CD is difficult to adopt. MinimumCD cuts through distracting or confusing complications. If you can do what MinimumCD says, you will be doing a better job. It gives us a clear, simple focus on the essentials of CD that can help teams to understand what really matters to build better software faster.
MinimumCD in the Media
- CodingBlocks Podcast, February 27, 2022: The host discuss their impressions of the project
- Tiny DevOps #21: Minimum Viable CD: Jonathan Hall talks to one of the core team about the goals of the project