~/talk

2 Hours to 10 Minutes: Building Rust Monorepos at Scale with Bazel RBE

links:none on file
slides:none on file

A Rust monorepo with ~170 crates moves CI from slow GitHub Actions to Prow on Kubernetes with Bazel + remote execution and a local NVMe content store, cutting median Bazel test time to 3 minutes from tens of minutes, generating ~5,000 actions and using content-addressed caching to avoid reruns. No-verdict runs drop from 18% to 6%, most tests run under Bazel while Cargo stays for live-service tests, and the system proves reproducible and practical.

AI-written summary · about

  1. 0:00Introduction and context
  2. 2:30Monorepo trade-offs in Rust
  3. 7:27Evolution of CI at Foresight
  4. 10:57Switching from GitHub Actions to Prow
  5. 13:51Building a custom Rust CI tool
  6. 16:19Introducing Bazel for Rust
  7. 21:58Current CI workflow with Bazel
  8. 25:56Performance gains with Bazel
  9. 27:41Future plans and developer workflow
  10. 29:05When to consider Bazel
  11. 30:10Q&A session
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.