[roll] Roll fuchsia [build][drivers] Use compat shard in generated manifests When building manifests, rather than hardcode boilerplate in the python script, the compat shard is used instead. Dynamic content is still added via python. Tested: fx test src/devices/tests/ Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/714803 Original-Revision: a50cd85827c6d273ce112afa99128c60054611b8 GitOrigin-RevId: 0c2d5c699122a5b04e8b4ae3e7dbbdad79d158ae Change-Id: Ib44b16438e44a54e926d94669cdedda9991d47d3
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.