[roll] Roll fuchsia [bazel] Use BAZEL_FUCHSIA_DISK_CACHE even for remote builds.

Bazel seems to work correctly when both --disk_cache and
remote builds are used at the same time. However, benchmarking
shows that it still favors the remote cache, which on my
workstation in Paris is significantly slower to access,
even when there are many cache hits.

It might be useful to look at the `bazel-remote` program
and see if it could be used as a proxy between a local
cache directory and the remote cache to speed things up.

Original-Bug: 499171347
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1563636
Original-Revision: 3337ff4487e3e6ea82a9d92947a9b3087452fa08
GitOrigin-RevId: 54ea96d2c0993fd983e16dfa7bb0db7c8468df5f
Change-Id: Ibf596a723a5a1a3853bb645e9401a4d59693dcb6
1 file changed
tree: 72d25803a0aa0b27e79eca62f92d3956e6a7066b
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cobalt
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance in one of the communication channels documented at get involved.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.