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

Geoffrey Martin-Noble via Phabricator via llvm-commits llvm-commits at lists.llvm.org
Wed May 17 15:40:43 PDT 2023

GMNGeoffrey added a comment.

@aeubanks wrote:

> 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?

Yes `--noremote_upload_local_results`

> I don't think we'd want non-CI users uploading to the cache.

For sure, that would be bad

> (the bots also use `--config=ci` and I believe a custom clang built by Chrome so you'd have to match that)

Yeah this is the containerization bit

> 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.

I don't think there's too much issue with a world-readable GCS bucket, especially if you don't allow anonymous access, so people have to authenticate themselves (although that also makes it more annoying to use and requires a gmail account). I think GCS can handle the traffic fine. We've got a few world-readable buckets in IREE for hosting misc binary files and such and we haven't had any issues.

  rG LLVM Github Monorepo



More information about the llvm-commits mailing list