AllDayDevOps: Crossing the CD Chasm
•
1 like•385 views
My #AllDayDevOps presentation on how to get started with Continuous Delivery
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (13)
Similar to AllDayDevOps: Crossing the CD Chasm
Similar to AllDayDevOps: Crossing the CD Chasm (20)
More from J. Paul Reed
Recently uploaded
Recently uploaded (20)
AllDayDevOps: Crossing the CD Chasm
- 1. J. Paul Reed Managing Partner • Release Engineering Approaches Crossing the CD Chasm November 15, 2016
- 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. Let’s Start with a Survey... @jpaulreed @AllDayDevOps
- 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. 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. 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
- 11. A Couple Possibilities @jpaulreed @AllDayDevOps
- 12. A Couple Possibilities @jpaulreed @AllDayDevOps
- 13. A Couple Possibilities @jpaulreed @AllDayDevOps
- 14. Let’s Build a Bridge! @jpaulreed @AllDayDevOps
- 15. Let’s Build a Bridge! @jpaulreed @AllDayDevOps
- 16. Let’s Build a Bridge! @jpaulreed @AllDayDevOps
- 17. Let’s Build a Bridge! @jpaulreed @AllDayDevOps
- 18. Let’s Build a Bridge! @jpaulreed @AllDayDevOps
- 19. Let’s Build a Bridge! @jpaulreed @AllDayDevOps
- 20. A Better Idea? @jpaulreed @AllDayDevOps
- 21. PREPPING FOR THE HIKE Crossing the Chasm ON THE TRAIL CAMP FIRE STORIES @jpaulreed @AllDayDevOps
- 22. Prepping for the Hike @jpaulreed @AllDayDevOps
- 23. The Right People @jpaulreed @AllDayDevOps
- 24. The Right People Developers • QA • Release Engineers • The “Business” @jpaulreed @AllDayDevOps
- 25. The Right Tools @jpaulreed @AllDayDevOps
- 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. PREPPING FOR THE HIKE Often Forgotten in CI Land • Configuration management • Backups • Connection to source code repositories • Access control @jpaulreed @AllDayDevOps
- 32. PREPPING FOR THE HIKE Telling Indicators • Possible to switch continuous integration software? • “Show me your CI slaves” • NTP (my favorite!) @jpaulreed @AllDayDevOps
- 33. What Happens When... @jpaulreed @AllDayDevOps
- 34. Integrating Streams of Change @jpaulreed @AllDayDevOps
- 35. On The Trail @jpaulreed @AllDayDevOps
- 36. Getting Started A Great Catalyst... To Avoid @jpaulreed @AllDayDevOps
- 40. Questions on Quality @jpaulreed @AllDayDevOps
- 41. ON THE TRAIL Continuous Quality • Start with The ComponentTM • Laser-focus on defect testing • Integration/systems testing • Fuzz testing @jpaulreed @AllDayDevOps
- 44. Flow Down the Mountain @jpaulreed @AllDayDevOps
- 46. Continuous Delivery = Ship Every Single Commit @jpaulreed @AllDayDevOps
- 49. Continuous Delivery is only for web applications @jpaulreed @AllDayDevOps
- 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
- 54. You can implement Continuous Delivery using the same QA/RelEng strategies as always @jpaulreed @AllDayDevOps
- 56. You can implement Continuous Delivery by yourself. Or without focused investment. @jpaulreed @AllDayDevOps
- 57. Hiking Alone is Dangerous @jpaulreed @AllDayDevOps
- 58. You can implement Continuous Delivery without an increase in transparency @jpaulreed @AllDayDevOps
- 59. “My Part Is Automated!” @jpaulreed @AllDayDevOps
- 60. “My Part Is Automated!” @jpaulreed @AllDayDevOps
- 61. Flow = Visibility @jpaulreed @AllDayDevOps
- 63. Won’t Be Easy... @jpaulreed @AllDayDevOps
- 64. But Worth It @jpaulreed @AllDayDevOps
- 65. J. Paul Reed Managing Partner • Release Engineering Approaches Thanks! @jpaulreed @AllDayDevOps