[roll] Roll fuchsia [bazel][assembly] Use bazel_build_group()

Use the new bazel_build_group() templates to build several
Bazel targets related to the same product bundle in a single
Bazel invocation (and thus Bazel analysis).

+ This requires creating a real Bazel target in the graph
  instead of using a label such as `//:UNUSED_TARGET` which
  ended up making the non-existing //BUILD.bazel file an
  input to the build group target.

+ Remove the "image_name" field in the product configuration
  of both the BUILD.gn and BUILD.bazel file, to ensure that
  the ZBI name is `fuchsia.zbi`, as it should be, instead
  of `fx_publish.zbi`.

Original-Bug: 352292703
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1079093
Original-Revision: e6e98a3578888a4b765fe2e6d3553a3c800f008b
GitOrigin-RevId: 6c928ed19a9790b2edad783c642a5e68dff34479
Change-Id: Ic343f4336883eb3418db910a8b299b6e5441415f
1 file changed
tree: 0ffabde994999613f97d5e921079af04ba5270ee
  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.