[roll] Roll fuchsia [scrutiny] Allow multiple component_tree_configs

As platform components with dynamic routing functionality are
introduced, Scrutiny will need a way to interpret what they can do
through a combination of platform and product specified
component_tree_config files.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1445907
Original-Revision: 26627ede098bbf0f75a7597a5c93ea06ae49607e
GitOrigin-RevId: 21f9e3808e1b373530c55162b6411d38337a29ac
Change-Id: Ibfb3e63c828898ff05b96e46a6f7f3edce5ed1b5
1 file changed
tree: 0cc46dce3094d1bbf6b64dcaedef12eb7ff04758
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. flower
  6. jiri.lock
  7. MILESTONE
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. 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.