Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

AllDayDevOps: Crossing the CD Chasm

154 views

Published on

My #AllDayDevOps presentation on how to get started with Continuous Delivery

Published in: Technology
  • Be the first to comment

  • Be the first to like this

AllDayDevOps: Crossing the CD Chasm

  1. 1. J. Paul Reed Managing Partner • Release Engineering Approaches Crossing the CD Chasm November  15,  2016
  2. 2. J. Paul Reed •@jpaulreed on •@shipshowpodcast alum •Fifteen years as a build/release engineer •Now a “DevOps consultant™” •Master’s candidate in Human Factors & Systems Safety @jpaulreed @AllDayDevOps
  3. 3. Let’s Start with a Survey... @jpaulreed @AllDayDevOps
  4. 4. Continuous Delivery @jpaulreed @AllDayDevOps
  5. 5. Continuous Delivery Deployment @jpaulreed @AllDayDevOps
  6. 6. Continuous Delivery Deployment Derpliveryment @jpaulreed @AllDayDevOps
  7. 7. Continuous Delivery Means Minimizing Lead Time From Idea To Production And Then Feeding Back To Idea Again. Rolf Andrew Russell, Thoughtworks ” “ @jpaulreed @AllDayDevOps
  8. 8. Continuous Delivery Is A Set Of Principles And Practices To Reduce The Cost, Time, And Risk Of Delivering Incremental Changes To Users. Jez Humble ” “ @jpaulreed @AllDayDevOps
  9. 9. Continuous Delivery Is Your Organization—Your Entire Organization—Caring About Release Engineering And Quality Assurance In A Way It Has Never Cared About Them Ever Before. Me ” “ @jpaulreed @AllDayDevOps
  10. 10. How Would You Get Across? @jpaulreed @AllDayDevOps
  11. 11. A Couple Possibilities @jpaulreed @AllDayDevOps
  12. 12. A Couple Possibilities @jpaulreed @AllDayDevOps
  13. 13. A Couple Possibilities @jpaulreed @AllDayDevOps
  14. 14. Let’s Build a Bridge! @jpaulreed @AllDayDevOps
  15. 15. Let’s Build a Bridge! @jpaulreed @AllDayDevOps
  16. 16. Let’s Build a Bridge! @jpaulreed @AllDayDevOps
  17. 17. Let’s Build a Bridge! @jpaulreed @AllDayDevOps
  18. 18. Let’s Build a Bridge! @jpaulreed @AllDayDevOps
  19. 19. Let’s Build a Bridge! @jpaulreed @AllDayDevOps
  20. 20. A Better Idea? @jpaulreed @AllDayDevOps
  21. 21. PREPPING FOR THE HIKE Crossing the Chasm ON THE TRAIL CAMP FIRE STORIES @jpaulreed @AllDayDevOps
  22. 22. Prepping for the Hike @jpaulreed @AllDayDevOps
  23. 23. The Right People @jpaulreed @AllDayDevOps
  24. 24. The Right People Developers • QA • Release Engineers • The “Business” @jpaulreed @AllDayDevOps
  25. 25. The Right Tools @jpaulreed @AllDayDevOps
  26. 26. Continuous... @jpaulreed @AllDayDevOps
  27. 27. Continuous... Integration? @jpaulreed @AllDayDevOps
  28. 28. Another Survey @jpaulreed @AllDayDevOps
  29. 29. Another Survey @jpaulreed @AllDayDevOps
  30. 30. PREPPING FOR THE HIKE Jez’s CI Gauntlet • Put your hands up if you do continuous integration • Put your hand down if all of the developers on your team don’t check into trunk/master at least once a day • Put your hand down unless every check-in triggers build... • ... followed by unit tests... • ... for the complete product • Put your hands down if broken builds are not fixed within 10 minutes @jpaulreed @AllDayDevOps
  31. 31. PREPPING FOR THE HIKE Often Forgotten in CI Land • Configuration management • Backups • Connection to source code repositories • Access control @jpaulreed @AllDayDevOps
  32. 32. PREPPING FOR THE HIKE Telling Indicators • Possible to switch continuous integration software? • “Show me your CI slaves” • NTP (my favorite!) @jpaulreed @AllDayDevOps
  33. 33. What Happens When... @jpaulreed @AllDayDevOps
  34. 34. Integrating Streams of Change @jpaulreed @AllDayDevOps
  35. 35. On The Trail @jpaulreed @AllDayDevOps
  36. 36. Getting Started A Great Catalyst... To Avoid @jpaulreed @AllDayDevOps
  37. 37. Rethinking Fundamentals @jpaulreed @AllDayDevOps
  38. 38. Rethinking Fundamentals @jpaulreed @AllDayDevOps
  39. 39. Rethinking Fundamentals @jpaulreed @AllDayDevOps
  40. 40. Questions on Quality @jpaulreed @AllDayDevOps
  41. 41. ON THE TRAIL Continuous Quality • Start with The ComponentTM • Laser-focus on defect testing • Integration/systems testing • Fuzz testing @jpaulreed @AllDayDevOps
  42. 42. On Silos @jpaulreed @AllDayDevOps
  43. 43. On Silos @jpaulreed @AllDayDevOps
  44. 44. Flow Down the Mountain @jpaulreed @AllDayDevOps
  45. 45. Campfire Stories @jpaulreed @AllDayDevOps
  46. 46. Continuous Delivery = Ship Every Single Commit @jpaulreed @AllDayDevOps
  47. 47. @jpaulreed @AllDayDevOps
  48. 48. Continuous Delivery requires Git @jpaulreed @AllDayDevOps
  49. 49. Continuous Delivery is only for web applications @jpaulreed @AllDayDevOps
  50. 50. Printers? @jpaulreed @AllDayDevOps
  51. 51. Core Internet Infrastructure? @jpaulreed @AllDayDevOps
  52. 52. "What's Important About Continuous Delivery: It's Not About How Fast You Can Turn The Crank, It's The Confidence With Which You Can [Turn That Crank]. Damon Edwards, Episode 15, The Ship Show ” “ @jpaulreed @AllDayDevOps
  53. 53. Serious Infrastructure @jpaulreed @AllDayDevOps
  54. 54. You can implement Continuous Delivery using the same QA/RelEng strategies as always @jpaulreed @AllDayDevOps
  55. 55. @jpaulreed @AllDayDevOps
  56. 56. You can implement Continuous Delivery by yourself. Or without focused investment. @jpaulreed @AllDayDevOps
  57. 57. Hiking Alone is Dangerous @jpaulreed @AllDayDevOps
  58. 58. You can implement Continuous Delivery without an increase in transparency @jpaulreed @AllDayDevOps
  59. 59. “My Part Is Automated!” @jpaulreed @AllDayDevOps
  60. 60. “My Part Is Automated!” @jpaulreed @AllDayDevOps
  61. 61. Flow = Visibility @jpaulreed @AllDayDevOps
  62. 62. Hiking the Chasm @jpaulreed @AllDayDevOps
  63. 63. Won’t Be Easy... @jpaulreed @AllDayDevOps
  64. 64. But Worth It @jpaulreed @AllDayDevOps
  65. 65. J. Paul Reed Managing Partner • Release Engineering Approaches Thanks! @jpaulreed @AllDayDevOps
  66. 66. Hikes Through Other Canyons jpaulreed.com/devops-in-practice jpaulreed.com/continuous-delivery-skeptics @jpaulreed @AllDayDevOps
  67. 67. November  15,  2016
  68. 68. November  15,  2016

×