Development, Review and Integration at Google scale
summary
Google runs one giant single repository served by piper, so every build references one authoritative revision and avoids package versioning conflicts. Engineers work in virtual workspaces and submit many small changes to keep reviews short; reviews use an internal tool and rely on automated testing. Builds use blaze with a distributed build cache and cloud builders, while test platforms named tap and guitar run unit, integration and multi-service end-to-end tests to catch regressions early.
AI-written summary · about
chapters (14)
- 0:00Intro
- 1:33Agenda
- 2:48Why do we care?
- 6:12The Goal
- 9:43Scaling up
- 10:31Performance
- 11:32Integration, Conflicts, Code Reusability
- 14:00Tests, tests, tests..
- 16:48The Culture - Maintaining excellence
- 26:13The Code - Single repository
- 29:01The Workspace - Clients in the Cloud
- 31:24The Build - Blaze & Forge
- 33:52The Tests - Blaze, TAP. Guitar
- 37:04The Review - Critique
related talks
38mGoogle's DevOps Culture
44mBuilding a Distributed Build System at Google Scale
38mSIG Release - Deep Dive: Release Engineering Subproject
53mVery Large Development: How to Run Code Review for 1000 Developers
42mHow DevOps Accelerates "Idea to Prod" at Google and What It Means to You
38mSIG Release Deep Dive
57mLarge-Scale Refactoring @ Google
39mMoving fast and staying aligned how automation powers progress