[roll] Roll fuchsia [build][bazel_sdk] Make directory optional in fuchsia_legacy_bundle() and fuchsia_platform_artifacts()

Compute the directory automatically if not provided when calling these
rules. This is done by scanning the 'files' filegroup for a file named
"assembly_config.json" and taking its parent path.

If the scan fails, a human-friendly error message is printed telling
the user to add an explicit 'directory' attribute value.

This will simplify target definitions with these rules in a future
CL that will move labels from @legacy_ninja_build_outputs to
@gn_targets.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1016253
Original-Revision: 3c61a3f0c540fe9935ef62d82fe972fd2ef14def
GitOrigin-RevId: eabb857336397a8f360cefc0378b59bdeb93c3eb
Change-Id: I130e3a469a640592834c653c116be7d62a378df2
1 file changed
tree: 734d9edc6fa3ba184394b0e70d7948b3a0a84cf0
  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 via the IRC channel #fuchsia on Freenode.

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.