Make local development (with Bazel) great again!
summary
Company moves a monorepo of ~300 backend devs and ~1,300 microservices off Maven to Bazel and builds IDE tooling so local work stops stalling on frequent syncs and build-file edits. Outcomes: autosync triggers partial syncs so tests and renames run immediately, depfixer scrapes compiler output to add labels (works but can be slow), autodep adds deps live during coding, and a global index lets autocomplete and refactor hooks update BUILD files; demos show tests passing and files edited without manual sync.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 5:40Bazel IntelliJ sync problems
- 12:27Adding dependencies struggles
- 17:07DepFixer and AutoDep
- 22:05Bazel refactoring challenges
- 24:50New targets and templates
- 27:17Red code and external deps
- 28:01Build file hygiene
- 33:42Summary and future plans
- 35:28Q&A
related talks
11mPerformant Bazel Builds for Web Monorepos at Scale
20mAdopting Bazel in a quickly scaling organization
31mBazel: Do We Really Need Another Build Tool?
18mFusing Bazel
41mThe wait is over. How to successfully migrate to Bazel from Maven or Gradle
36m2 Hours to 10 Minutes: Building Rust Monorepos at Scale with Bazel RBE
01h 31mBazel
34mBuilding Real-time Systems with Bazel