Six learnings in moving to a Bazel-based CI system + Q&A
summary
Wix migrates its backend CI from Maven/TeamCity to Bazel, using an open‑source migration tool called Exodus to generate build/workspace files and then a small team to fix edge cases; total codebase is ~5M LOC across ~1,000 repos consolidated to ~50. CI feedback shrinks from hours to 5–10 minutes cached, deployable creation to 15–25 minutes (targeting half that), and one repo yielded 2,300 Bazel targets from 200 Maven modules; key infrastructure: remote cache + remote execution, prepopulated Maven/Docker caches, parallel new-and-old pipelines for safe rollout.
AI-written summary · about
chapters (10)
- 0:00Faster CI with Bazel
- 3:56Why migrate from Maven
- 8:31Migration tool: Exodus
- 10:40Measure before and after
- 13:50Local dev experience
- 16:18Parallel CI pipelines
- 19:08Speed with caching
- 22:18Poly-repo to Bazel
- 31:12Where Wix stands now and future work
- 32:42Q&A
related talks
41mThe wait is over. How to successfully migrate to Bazel from Maven or Gradle
20mAdopting Bazel in a quickly scaling organization
25mInteroperating Bazel and Other Build Systems
18mFusing Bazel
34mBuilding Real-time Systems with Bazel
01h 31mBazel
48mCI With Bazel (Why Selenium is Using It & You Should Too)
01h 01mIntroduction to Bazel