[roll] Roll fuchsia [bazel] Avoid hashing the same content twice during workspace setup.

The content hash files for `fuchsia_sdk` and `fuchsia_in_tree_idk`
are the same, which resulted in hashing the content of the same IDK
directory twice when this script was running.

As a minor performance improvement, ensure the hashing of the content
only happens once, and create a symlink from one content file to the
other.

NOTE: The `bazel_action.py` script depends on the name of the content
files to match those of the repository that depend on them.

NO_IFTTT=no real need to change toplevel.WORKSPACE.bazel here!

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1165953
Original-Revision: dccd2da5868a8caf2c58c91c185089c01aae8516
GitOrigin-RevId: 4a74402605586f6857e62dd8a9f4ea88a03abb3d
Change-Id: Ie54b5e8a283fbef2b6ffda0d41abc4d56a400450
1 file changed
tree: 876788aa785319263d15e667acbfd0b9d72ace6f
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. toolchain
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.