DevOps & Software Delivery in a Global Pandemic
Slide 1
Slide 2
Slide 3
“
Slide 4
performance described vs performance derived
Slide 5
Jeremy Meiss Director, DevRel & Community
Slide 6
Dataset 257 mil+ 44,000+ 290,000+ 1,000x workflows orgs projects Larger than surveys 6
Slide 7
Four classic metrics Deployment frequency Lead time to change Change failure rate Recovery from failure time
Slide 8
CI/CD Benchmarks for high performance teams Suggested Benchmarks Throughput The average number of workflow runs per day Duration The average length of time for a workflow to run Mean time to recovery The average time between failures & their next success Success rate The number of successful runs / the total number of runs over a period of time Merge on any pull request 10 minutes Under 1 hour 90% or better on default branch
Slide 9
9
Slide 10
The Data
Slide 11
Photo by: Matthew Henry 11
Slide 12
Throughput the average number of workflow runs per day 12
Slide 13
Throughput
Slide 14
Throughput 14
Slide 15
Throughput 15
Slide 16
Most teams are not deploying dozens of times per day
Slide 17
Image by Pawan Kolhe from Pixabay
Slide 18
Duration Image by Pawan Kolhe from Pixabay the length of time it takes for a workflow to run 18
Slide 19
Duration Image by Pawan Kolhe from Pixabay 19
Slide 20
Duration Image by Pawan Kolhe from Pixabay 20
Slide 21
Duration Image by Pawan Kolhe from Pixabay 21
Slide 22
Photo by Brett Sayles from Pexels
Slide 23
Mean time to recovery average time between a pipeline’s failure and its next success
Slide 24
Mean time to recovery shortest MTTR ∝ Duration
Slide 25
“…the most robust — and certainly the fastest — solution to a broken build is to simply revert the offending commit, allowing troubleshooting to happen in a way that doesn’t interfere with the rest of the team. You can’t know whether a new build works or not unless you’re starting from a known good position, which means you should never allow a new build to start on a red build unless it’s explicitly designed to fix it, and it’s hard to imagine a commit more likely to fix a broken build than simply reverting the one that broke it to begin with.” - Brandon Byers, Head of Technology, NA @ Thoughtworks Photo by Brett Sayles from Pexels 25
Slide 26
Recovery Time
Slide 27
Recovery Time
Slide 28
Recovery Time
Slide 29
Recovery Time
Slide 30
Photo by Lukas from Pexels
Slide 31
Success rate The number of passing runs ÷ total number of runs over a period of time 31
Slide 32
Success rate 32
Slide 33
Success rate 33
Slide 34
Success rate 34
Slide 35
Duration The average length of time for a workflow to run TTR The average time between failures & their next success 2019 (median) 2020 (median) This Year (median) Benchmark 3.38 min 3.96 min 3.7 min 5-10 minutes 52.5 55.11 73.6 min < 60 minutes 77% Average should be +90% on default branch 1.43/day As often as your business requires not a function of your tooling Success rate The number of successful runs / the total number of runs over a period of time 60% 61% Throughput The average number of workflow runs per day 0.80/day 0.70/day 35
Slide 36
Extra Insights
Slide 37
202x has been a year.
Slide 38
“Don’t deploy on Friday” is not a thing.
Slide 39
“Don’t Deploy on Friday” is not a thing ○ 70% less Throughput on weekends ○ 11% less Throughput on Friday (UTC) ○ 9% less Throughput on Monday (UTC)
Slide 40
Language shifts over the last few years 40
Slide 41
41
Slide 42
42
Slide 43
43
Slide 44
44
Slide 45
Vertical splits 45
Slide 46
Elite Performer validation 50th percentile on CircleCI fit into the “Elite performer” category on the 2021 State of DevOps report
Slide 47
2020 Report Full 2022 Report https://circle.ci/ssd2020 https://circle.ci/ssd2022 47
Slide 48
Timeline.jerdog.me Thank you. For feedback and swag: circle.ci/jeremy IAmJerdog jerdog /in/jeremymeiss
