4 ms·
I migrated my team of ~20 developers to Bazel, and I have to say I don’t think it is that complex. Not only don’t we have 3 full time engineers devoted to Bazel
by dieortin 2y ago
I migrated my team of ~20 developers to Bazel, and I have to say I don’t think it is that complex. Not only don’t we have 3 full time engineers devoted to Bazel, as I do everything myself, but in fact it’s not even my main role to maintain the build system.
We do not use some of the more complex features like remote execution, but we do enjoy all the other features including remote caching. We reduced build times by 92% after the migration.
So my advice would be, try it and see for yourself if you think it’s worth the hassle. For my team, it definitely has been.
- m1keil 2y agoSo what happens if you leave tomorrow? Will your team be able to pick up where you left off?
- binary132 2y agoIt is really not that hard to grok and use. I think cmake is actually a bit harder. It doesn’t hurt that bazel builds are implemented in starlark instead of a zany state manipulation language-that-isn’t-a-language.
- liontwist 2y agoI would hope that a build system for 20 people takes zero time to maintain.