Consider making CI bazel cache public for read only access

Open
#356 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
gcp, java
Domain
build-system, ci-cd, cloud

Research direction

Start with the Bazel remote-caching documentation linked in the issue, then inspect the repository's CI configuration and any bazelrc or Maven profile. Determine whether the GCP bucket can safely allow read-only access for local builds and how that access would be configured. Done means local builds can use the CI cache without write permissions or compromising the bucket.

Written by the indexing model from the issue text.

Description

Bazel allows you to use the build cache in a read-only manner see here. It would be very helpful for local builds if we could make the cache used by the CI available in read only mode for local builds, and potentially automatically set that up (via a bazelrc or maven profile). Currently building from scratch takes several hours for me, which is quite a pain. It would require changing the permissions on the GCP bucket though and I'm not sure if that's something we can do.

cc @karllessard

Dominant language
Java
Stars
928
Forks
227
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from tensorflow/java

All issues in tensorflow/java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.