The Death Of Continuous Integration

The Death Of Continuous Integration

As delivery teams mature and adopt Continuous Delivery they will explicitly discard practices that have become more costly over time. However, many teams today are implicitly discarding Continuous Integration, due to ever-easier Feature Branching and an under-appreciation of Trunk Based Development. What are the consequences of this Continuous Isolation trend for agile development and Continuous Delivery?

In this talk Steve Smith will describe how ever-better Feature Branching tooling has harmed Continuous Integration, compare the cost vs. value of Feature Branching and Trunk Based Development, and explain why Continuous Delivery without Continuous Integration is asking for trouble.

622051376c3b381ef1c786036011112d?s=128

Steve Smith

August 25, 2015
Tweet

Transcript

  1. The Death Of Continuous Integration Steve Smith @SteveSmithCD hello@continuousdeliveryconsulting.com

  2. Steve Smith Continuous Delivery consultant and trainer Author of “Measuring

    Continuous Delivery” Co-author of “Build Quality In” b: www.continuousdeliveryconsulting.com e: hello@continuousdeliveryconsulting.com t: @SteveSmithCD Associated with
  3. Continuous Delivery “The Deployment Pipeline is in essence the principle

    of Continuous Integration taken to its logical conclusion” Dave Farley and Jez Humble A holistic approach to reducing time to market Continuous Delivery needs a releasable codebase Continuous Integration minimises integration costs Continuous Delivery requires Continuous Integration
  4. Continuous Integration “Members of a team integrate their work frequently,

    usually each person integrates at least daily” Martin Fowler Continuous Integration is a shared mindset All developers commit to Trunk at least once a day Low integration costs enables predictable flow Continuous Integration is valuable – and imperilled
  5. Release Feature Branching

  6. Release Feature Branching

  7. Trunk Based Development

  8. Trunk Based Development

  9. Trunk Based Development

  10. Trunk Based Development

  11. Trunk Based Development

  12. Continuous Delivery at HP “Continuous Integration and quality are everything

    together, and nothing without each other” Gary Gruver, Mike Young, and Pat Fulghum 2008: 400+ engineers on 10m lines of firmware 10 Release Feature Branches 1 week build, 6 weeks regression testing Engineers: 25% product support, 5% innovation
  13. Continuous Delivery at HP “Continuous Integration and quality are everything

    together, and nothing without each other” Gary Gruver, Mike Young, and Pat Fulghum 2012: Huge investment in Continuous Integration 1 Trunk with products re-architected as config 3 hour build, 24 hours testing, 10-15 builds a day Engineers: 5% product support, 40% innovation
  14. Build Feature Branching

  15. Build Feature Branching

  16. Build Feature Branching

  17. Build Feature Branching

  18. Build Feature Branching

  19. Build Feature Branching

  20. Build Feature Branching

  21. Build Feature Branching

  22. Build Feature Branching

  23. Build Feature Branching

  24. The Death Of Continuous Integration

  25. The Death Of Continuous Integration

  26. The Death Of Continuous Integration

  27. The Death Of Continuous Integration Steve Smith @SteveSmithCD hello@continuousdeliveryconsulting.com