[roll] Roll fuchsia [assembly] Use explicit images config if available

If an explicit images config is provided, always use that instead of the
GN-generated one. Continue to compare equivalency against a GN-generated
one unless use_explicit_images_config_only=true.

This allows us to migrate test assemblies over to an explicit images
config without creating a bazillion hardcoded explicit images configs.
The test assemblies currently use ambient GN args, therefore have a
bazillion different combinations. They don't need to, though!

Original-Bug: b/290250084
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/882033
Original-Revision: 92776297570ed2b584e141d4f167be0b89bf73b9
GitOrigin-RevId: eb3f3e98a9d8d30ac7c4f0ce48e039da5ae3b49d
Change-Id: I0259fb07f0d8eca62201c8fcd80623aa7698ed80
1 file changed
tree: 4c4fb7a339e7449aad0f9aa65d489ac1a2bbd520
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
  14. 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.