Bazel Migration Patterns
summary
Practical migration advice: run a thorough discovery phase to map the legacy build, surface costly pain points and size effort (expect >12 months or ~1.5 engineers for nontrivial repos), prototype risky pieces, and prove value early by enabling remote cache and execution so CI and local dev show real speedups. Use patterns like deploy artifacts first, parallel builds, inside-out or outside-in, coarse-grain-first or monorepo onboarding; measure before/after (Angular reports ~30→5 minute CI for packages) and defer tricky platform rules.
AI-written summary · about
chapters (5)
- 0:00Introduction
- 3:36Why not migrate now
- 13:23Migration planning
- 26:18Evaluating patterns
- 40:40Key migration steps
related talks
41mThe wait is over. How to successfully migrate to Bazel from Maven or Gradle
20mAdopting Bazel in a quickly scaling organization
23mWhy you need a build system, and why it should be Bazel
25mInteroperating Bazel and Other Build Systems
01h 31mBazel
31mFork, PR and Merge
23mWalk, Run, Fly - Take your build pipeline to the next level!
18mFusing Bazel