Faster Builds With Remote Execution and Caching
summary
Describes Google Cloud Remote Build Execution (RBE), an alpha, hosted implementation of the open Remote Execution API that uses Docker image hashes and toolchain descriptions to run Bazel builds and tests at cloud scale. Claims include 80% average build time reduction for TensorFlow (≈50 min → ≈5 min), Android Studio increasing presubmit coverage more than 4x, Angular CI dropping ~1h → 15m, and Absil C++ going 88s → 51s with remote cache and 23s with exec+cache. Advises CI-first onboarding, cache silo key and Docker image hash for hermeticity and permissions.
AI-written summary · about
chapters (9)
- 0:00Remote execution and caching intro
- 1:49How remote exec and cache work
- 3:12Why remote builds are faster
- 4:56Benefits of remote builds
- 7:27Google Cloud's remote build service
- 10:15Customer results and benchmarks
- 12:41Onboarding remote cache and exec
- 19:02Adopt remote execution steps
- 24:15Summary
related talks
11mIntroducing Remote Bazel
23mWalk, Run, Fly - Take your build pipeline to the next level!
50mBuilding on Key – Keeping your Actions and Remote Executions in Tune + Q&A
38mBuilding Self Driving Cars with Bazel + Q&A
01h 31mBazel
10m{ Fast, Cost-effective } – Choose Two
28mBazel Remote Execution and Remote Caching
41mGoogle Container Tools: Develop Efficiently [...]
