[PATCH] D136496: [bazel] Make labels to third-party dependencies explicit

[Arthur Eubanks via Phabricator via llvm-commits]

aeubanks added a comment.

In D136496#4348280 <https://reviews.llvm.org/D136496#4348280>, @GMNGeoffrey wrote:

> In D136496#4294766 <https://reviews.llvm.org/D136496#4294766>, @aaronmondal wrote:
>
>> We're currently experimenting with caching and remote execution to see wether the cloud infra for an open-read remote Bazel cache for LLVM would be sustainable. If it is, we'd have a way to reduce the "build" time for LLVM Bazel users to ~2 min on a laptop from an empty local cache and some CI runtimes to potentially less than that.
>
> The CI is already using a remote cache and it should be possible to make that remote cache available to anyone. The tricky bit is just that for the caching to be effective it needs to be from a sufficiently similar software environment. Containerization could help with that. @aeubanks are you still making improvements to the LLVM Bazel infra?

I haven't done anything in a while (it's been chugging along pretty well on its own), but yeah I still technically own the bazel bots.
Does bazel allow read-only access to a remote cache? Or does it assume that you can write to it as well? I don't think we'd want non-CI users uploading to the cache.
(the bots also use `--config=ci` and I believe a custom clang built by Chrome so you'd have to match that)

Who is "we" in this case? If it's a company, it seems doable to have your own GCS (or whatever) remote cache and make everybody + CI use the same configuration. A world-usable one probably requires more thought.


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D136496/new/

https://reviews.llvm.org/D136496