[roll] Roll fuchsia [assembly] Eng artifacts are included in all platform artifacts Assembly already does the filtering and build type checking instead of GN. This is more powerful because it works in any build system and in any repository. This is the first step towards deleting build-type-specific platform artifacts, which simplifies the story of our platform and mirrors how OOT products actually use the platform. This change broke license accumulation because the license scripts walk the GN dependency graph and require all artifacts to have proper licenses. We want to ignore all artifacts that do not go into user builds, therefore I added some logic that adds a GN metadata barrier for AIBs that will never appear in user builds. Original-Bug: 474331015 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1504102 Original-Revision: 239345c08b6ad1c17712bff7ba6ed3a7a0d9326e GitOrigin-RevId: 9837b6c0a5d08ed7bcaf9939699295587a9fd986 Change-Id: I09b78280ad9d7e5d951d3fb782dc3c7541f95a83
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 in one of the communication channels documented at get involved.
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.