Running a Start-up on Bazel

on YouTube ↗27m

" summary

A 10‑engineer company runs Bazel on roughly 1 MM LOC across about 850 build files and ~3600 targets, migrating Go first (live May 2022) and using Gazelle for autogeneration. Remote GCS caching plus stateful CI runners yields full‑repo builds in under 10 minutes. Kotlin multiplatform gaps force custom rules and hosting Gradle inside Bazel; developer pain around IDE previews leads to a forked Android Studio plugin to restore Compose and XML tooling.

AI-written summary · about

" chapters (22)

1. 0:00Introduction
2. 0:43What this talk is not
3. 1:05Who are Ergatta
4. 2:31Repositories
5. 4:44Team Size
6. 6:12Starting with Bazel
7. 7:10Vertical scale
8. 7:36What do we like
9. 7:51GCS Cache
10. 8:41CI
11. 8:56Rules
12. 10:03Deploying
13. 11:04Slack Group
14. 12:38What we dont like
15. 15:22How to make it work
16. 15:46Get Scrappy
17. 16:27Build Files
18. 16:59Community
19. 17:48Benefits of Bazel
20. 18:01How would you do it again
21. 20:09Would you start another company today
22. 21:25Questions