Most of what this article seems to be saying is that Uber wasn't using all the features of bazel (and their setup also predates some of them), and as they've st

Most of what this article seems to be saying is that Uber wasn't using all the features of bazel (and their setup also predates some of them), and as they've started to use them things are getting a lot faster. Prior to doing so they were hacking around it like controlling when folks could land large changes. The rest of the article is about their transition from their legacy infra like Jenkins to more modern and flexible things like buildkite (which is of course relevant for anyone in a similar transition). If your company/project starts with bazel + remote cache + RBE you're pretty close to the end state they're trying to get to. See also for OSS and paid solutions: https://bazel.build/community/remote-execution-services https://bazel.build/community/remote-execution-services