Breaking out of the cage: move complex development to GitHub
summary
Migrating YDB’s main development branch to GitHub actually moves the source-of-truth, CI, and builds off proprietary infrastructure: GitHub Actions describe workflows, CMake builds are generated from the internal system, YATool is adapted for public runners, artifacts and logs live on S3, and a remote Bazel cache cuts full builds from 2.5 hours → 2 minutes on cache hits. The project handles 60K+ tests, ~100 developers retooled, and production-scale installs up to 5,000 nodes while using Testmo for historical test reporting.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:17YDB open source journey
- 3:01Publishing YDB on GitHub
- 8:42Detaching from corporate context
- 13:37Adapting build and test systems
- 18:55Full GitHub development
- 25:54Achievements and future
- 26:34Key takeaways
related talks
17mBuilding Secure Open Source Communities From the Ground Up
57mOpen Source at commercial organisations
45mA Call to (GitHub) Actions!
47mTales from the Dev Side: What Went Wrong, What We Fixe & What You Can Steal
42mMake local development (with Bazel) great again!
30mRelease Early and Release Often: Reducing deployment friction
32m“The Yahoo! Story” How Yahoo! Embraced Automated Testing to...
35mTesting in Production: there is a better way