[roll] Roll fuchsia [assembly] Product configs are stored in hermetic dirs

The product config and associated files are now copied into a hermetic
directory that can be passed between bazel rules and between
repositories.

A small tool `assembly_generate_config` is used to construct the
product config and to run hybrid assembly and replace packages in an
existing product config.

Original-Bug: 390189313
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1191637
Original-Revision: 47268a586e766bf4436cfe7279d8d077b9a3df23
GitOrigin-RevId: 8dd9ae1dd751b955980f1c43870d317b68659775
Change-Id: I860b53c90f1a7775dfdbb33db6a3e6a601947c09
1 file changed
tree: 1c24fa36fb852b64491934a0695fdabb83e024ab
  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.