[twunde]

I've used pants at a small company <10 engineers and worked at a company migrating to Bazel with 200+ engineers. Bazel used to take a dedicated engineer 3-6+ months to bootstrap the full setup (creating the build files, seeing up the Bazel server, updating CI to use Bazel correctly including caching) especially since the docs weren't great from what I remember. I suspect that the time could be cut down by now especially if someone experienced with it does the implementation. Given the amount of time necessary for the setup, it typically makes sense for companies with monorepos with 50+ engineers although existing expertise would change the equation.

[LargeTomato]

The docs are a massive problem. It's hard to do anything except the bare minimum of compiling code.

A lot of the isolation and visibility control in bazel is totally useless outside of big companies.

[grrandalf]

Thanks! Do you have any thoughts to share on reasons for the migration to Bazel?

3-6 mo of one engineer to migrate to something so hardcore as Bazel seems very good actually, especially since it seems they Did It Right. The flows in 200-engineer size org can be quite complicated.