Google's DevOps Culture
summary
Google describes a developer platform that automates away DevOps overhead for a 700+ engineer org, using Bazel, Spinnaker and CI that runs roughly 800,000 builds and 150 million tests to support 45,000 submits and 20,000 code reviews per workday. Developers get search across a 15M‑line repo, pre-submit checks, robot reviews, flaky‑test isolation and intelligence test selection; rolling releases, on‑call playbooks and blameless postmortems close the loop so failures are fixed and learned from.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 5:05People are the core of DevOps
- 11:33Engineering culture at Google
- 17:59Developer workflow and automation
- 25:16Incident response and postmortems
- 31:44Empowering developers and accountability
- 34:16Challenges and future of DevOps
related talks
42mHow DevOps Accelerates "Idea to Prod" at Google and What It Means to You
39mDevelopment, Review and Integration at Google scale
48mDevOps Culture & Practices to Create Flow
33mMeasuring DevOps
34mFrom Dev to DevOps
39mOops. I broke the Google, now what?
44mDevSecOps: Balancing Agility, Security & Stability in a Continuous Software Business
40mHow Google SRE and developers work together
