Introducing Remote Bazel
summary
Remote Bazel runs the Bazel client server and commands remotely so CI and dev machines reuse a warm analysis workspace stored in a remote cache, using Firecracker snapshotting and RBE-style remote execution to clone VM workspaces. BuildBuddy reports an 8× reduction in median CI duration, typical builds dropping from ~4 minutes to ~20 seconds and a customer moving from 10m to 1m40s. Access happens via BB CLI or curl, remote Runners stream logs, mirror local git diffs, and support arbitrary bash blocks and verified builds.
AI-written summary · about
chapters (13)
- 0:00Remote Bazel intro
- 0:41Why Remote Bazel
- 1:46Reusing CI workspaces
- 2:47Reducing build latency
- 3:28Performance improvements
- 4:29CI workflow integration
- 5:14Cross-platform dev
- 6:16Workspace sync
- 7:00Cost savings & access
- 8:03Debugging & parallel builds
- 8:46New UI features
- 9:29Implementation overview
- 9:50Try Remote Bazel
related talks
24mFaster Builds With Remote Execution and Caching
31mBuilding a great CI w/ Bazel
20mAdopting Bazel in a quickly scaling organization
38mBuilding Self Driving Cars with Bazel + Q&A
01h 31mBazel
28mBazel Remote Execution and Remote Caching
50mBuilding on Key – Keeping your Actions and Remote Executions in Tune + Q&A
31mHey Dad, What's Bazel?