[roll] Roll fuchsia [scrutiny] Generate platform scrutiny configs from AIBs

To quickly re-generate the goldens add this GN arg:
  update_goldens = true

and build:
  fx build bundles/assembly

The scrutiny configs are added to the bazel sdk and added to the
scrutiny verifiers by the fuchsia_product_bundle rule. This allows the
platform engineers to update their code without needing soft transitions
with vendor repos.

Original-Bug: b/302150846
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/961356
Original-Revision: a4edb1a929a7a3ff115944564a991a2abf6aa6bc
GitOrigin-RevId: dc318dbdb5fda54889cef90a6a5870a78919adfd
Change-Id: I9bd72fdfac952a78d00ab038f530f099e94577e2
1 file changed
tree: 4c13778b9b0c615832eba64c600f57d32354c58e
  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.