[roll] Roll fuchsia [bazel] Add fuchsia_repository_keys rule This adds some validation on the JSON files provided, make sure the keys provided matches expectation of the tool used [0]. Plus, it makes sure all key files used are correctly tracked by Bazel, so incremental build works correctly. Before this change, `repository_keys` from `fuchsia_product_bundles` asks for a directory, and it doesn't know about its contents. [0] https://cs.opensource.google/fuchsia/fuchsia/+/main:src/sys/pkg/lib/fuchsia-repo/src/repo_keys.rs;l=70;drc=9e27d52b46f87ddbeea8399ef672aec83bff5a40 Original-Bug: 119892 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/801108 Original-Revision: dda98c60bf114a98dc9fb90914bfa9b6cf6f3645 GitOrigin-RevId: cc579ddbaaf089639cb6feba1c29ab86de0c08e7 Change-Id: I572bc1328e5d7acf49b39604c3a811726d8cacc4
This repository contains Fuchsia's Global Integration manifest files.
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.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.