Very Large Development: How to Run Code Review for 1000 Developers
summary
OpenStack grows from ~60 to ~1,241 active developers with ~1.4M lines of code and ~2,000 commits per month and the review system evolves to keep trunk deployable. Automated gating uses Gerrit + git-review and staged merges via Zuul gating with DevStack integration VMs, tox and testrepository for parallel tests, and flightgate/flake8/hacking for style enforcement. Logs feed Elasticsearch for automated failure classification and recheck/elastic recheck reruns transient failures. Outcome is continuous merging, far fewer trunk breaks and an integration test bill around $100k.
AI-written summary · about
chapters (7)
- 0:00Start
- 3:22DEPLOYMENT SCALE THE DATA CENTER
- 3:56BY THE NUMBERS
- 4:38GRAPHS
- 5:14PROS AND CONS
- 7:50WHERE WE STARTED LAUNCHPAD (BZR AND ALL) (3 YEARS AGO)
- 22:53TESTING AUTOMATED CODE QUALITY CHECKS
related talks
01h 02mEffective Code Review
44mEffective Code Review
28mFrom Startup to Scale Up: How to Scale Engineering teams
42mA Modern Development Culture for a Modern Development Process.
39mDevelopment, Review and Integration at Google scale
47mScaling Your Engineering System
43mCode quality as an engine of your IT business
33mCode Review for Test Automation