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
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
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
41. ON THE TRAIL
Continuous Quality
• Start with The
ComponentTM
• Laser-focus on defect
testing
• Integration/systems
testing
• Fuzz testing
@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