Provide Bazel cache for TensorFlow builds
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 311
- Forks
- 139
- Avg merge
- 1h 28m
- Merged PRs (30d)
- 1
Description
Providing a TensorFlow build cache could be very helpful to external developers, and lower the barrier to entry of contributing to TF.
Some ideas for this we've discussed before are:
- Offer Bazel RBE resources on behalf of SIG Build. This service is in alpha on GCP.
- Provide a read-only build cache in a GCP bucket.
- Provide
devel_cacheDocker images containing a build cache (these could be very large) - Provide code-and-cache volumes for the docker
develimages.
See also:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked TensorFlow issues and the referenced Bazel remote-execution and remote-caching documentation. The issue lists several possible approaches rather than a defined entry point; done would require selecting and implementing a supported cache or build-resource solution for external TensorFlow contributors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, google-cloud
- Domain
- build-system, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100