[roll] Roll fuchsia [bazel_migration] Break up bazel build groups for product bundles

Break up the product bundle build group into a series of separate Bazel
targets that are separately depended on, to allow workflows like 'fx
publish cache` to once again operate without needing to construct the
full product bundle.

Original-Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1797277
Original-Original-Revision: d65782f242fa2849b822c585640c01e3ae3cd5ae
GitOrigin-RevId: 6f66b91951e869f48cc0d6da946c40434b73fc6a
Change-Id: Ibbd6bff005e56dfa4476068a3e05c66a520a2579
Reviewed-on: https://fuchsia-review.googlesource.com/c/integration/+/1800282
Cr-Commit-Position: refs/heads/main@{#201066}
1 file changed
tree: 41ab9c6409fe72891850fba2a2f76faa24bc3641
  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.