[roll] Roll infra/recipes [artifact_versioning] Allow preflighting artifacts This change introduces `api.artifact_versioning.register_artifact_preflight`, allowing artifacts to be validated earlier in CQ without registering them with the prod/preprod upstream backend endpoints. Specifically this will help us catch cases where multiple boards (eg: `sorrel` and `sorrel_recovery`) are reported to have the same unique MOS identifier (`name_sanitized` in the output of `ffx --machine json product get-version`) which has caused non-blocking builder failures in our canary assembly artifact release builders. Note: This approach cannot account for cross-builder collisions (eg: `vim3` and `vim3-vg`, which are reported across 2 different builders). Also adds `api.artifact_versioning.get_artifact_metadata`, enabling callers to determine whether an artifact path is a supported assembly artifact with metadata. Original-Bug: 444492378, 434965053 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/1366556 Original-Revision: 1e8a7df201ebd3d0dd1fe3b1d55b23a8b4add921 GitOrigin-RevId: aa6e556ed02a5354e4607f7022a48e10a618de9d Change-Id: I9658c6ee0493b82a13dc8bd0492238ab715a16c2
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.