Working with Alternative Build Systems
summary
At Uber Gradle configuration hits five plus minutes and a full sync once took an hour and a half on a 2,000+ module codebase, so the company converts projects to Buck with an OkBuck bridge and is migrating to Bazel; builds become hermetic, reproducible and much faster via Starlark rules, remote caching and remote execution, and tooling like bulldozer removes unused deps across 2000+ Gradle modules, OkBuck conversion and a codebase with 17,000 targets.
AI-written summary · about
chapters (9)
- 0:00Introduction and context
- 1:03Gradle issues at scale
- 11:28Starlark and alternative systems
- 16:21Build files with Starlark
- 21:37Cross-language support
- 27:17Organizational challenges
- 32:33Benefits at scale
- 35:00Downsides and trade-offs
- 37:28Should you switch?
related talks
41mBreaking the build
28mFast reliable Swift builds with Buck
20mAdopting Bazel in a quickly scaling organization
01h 00mAndroid builds
41mDude, Where's My Build? Android CI/CD at Uber
41mThe wait is over. How to successfully migrate to Bazel from Maven or Gradle
43mBetter, Faster, and Stronger CI/CD Pipeline
01h 31mBazel