Completed
Recovery Time decreases with increased team size (up to 200)
Class Central Classrooms beta
YouTube playlists curated by Class Central.
Classroom Contents
CNCF Member Webinar - DevOps from a Different Data-set
Automatically move to the next video in the Classroom when playback concludes
- 1 Intro
- 2 Performance derived vs performance described
- 3 160,000 projects
- 4 What's changed year over year?
- 5 Most projects configured to run per push to git server
- 6 Primary application or service you work on
- 7 How long does it take to get results?
- 8 % of builds finish in 12 seconds
- 9 Half of all builds finish in under 4 minutes
- 10 How often does your pipeline complete with a green status?
- 11 Time a pipeline sits in a failure state
- 12 Peak Throughput was April 2020
- 13 After April, Throughput falls a bit
- 14 Hypothesis: people working hard on core business stability
- 15 Hypothesis: Fewer distractions working at home
- 16 Branch Information
- 17 Success Rate is 80% on the default branch at 50th percentile and 100% for 75th percentile and above
- 18 Success Rate at 50p is 80% for default and 58% for non-default branches
- 19 Duration on default branches are faster at every percentile.
- 20 Recovery Time is lower on default branch at every percentile.
- 21 What development practices definitively work?
- 22 Success Rate does not correlate with company size
- 23 Duration is longest for teams of one
- 24 Recovery Time decreases with increased team size (up to 200)
- 25 Longest Recovery Times are from teams of one.
- 26 Performance is better with more than one contributor as shown by multiple indicators
- 27 Software is collaborative
- 28 % less Throughput
- 29 Final Thoughts
- 30 More collaborators means better outcomes
