The wait is over. How to successfully migrate to Bazel from Maven or Gradle
summary
Wix migrates 700+ microservices and 10M lines to Bazel and cuts a 45-minute full Maven build to under a minute for typical changes, with clean Bazel builds dropping to 20 minutes locally, 8.5 minutes on remote workers, and cached runs to seconds. Migration uses an automatic tool Exodus to generate package-level targets, embraces remote build execution with hundreds of workers, adopts a mono-repo/consolidation strategy, enforces a one-version third-party policy, and notes Mac sandbox and IDE integration trade-offs.
AI-written summary · about
chapters (22)
- 0:00Start
- 0:06Improve the Development Velocity
- 4:07What Is a Rule
- 5:16Java
- 11:09Dynamic Execution
- 15:21Choose the Hilarity for the Migration
- 15:35Performance Gain
- 16:00Ease of Migration
- 17:00Demo of How To Do the Migration Automatically with Exodus
- 17:39Run the Maven Install Command
- 17:59Setup the Scala Maven Plug
- 19:24Build Configurations
- 19:57The Package Level Dependencies
- 23:08The Amount of Source Control Repositories
- 24:21Challenges
- 27:14Which Ci Server To Run
- 28:27Dashboard
- 29:13Remote Build Execution
- 30:13Your Local Dev Experience
- 32:09Intellij Support
- 35:25Third Party Version Resolution
- 40:24Explicitly Declare both Compile Time Dependencies and Runtime Dependencies
related talks
40mSix learnings in moving to a Bazel-based CI system + Q&A
20mAdopting Bazel in a quickly scaling organization
31mGradle to Bazel + Q&A
25mInteroperating Bazel and Other Build Systems
42mMake local development (with Bazel) great again!
43mBazel Migration Patterns
01h 01mIntroduction to Bazel
18mFusing Bazel