commit | 77e13bd606c8ca8214f7604dbe880807788aee37 | [log] [tgz] |
---|---|---|
author | Drew Roen <drewroen@google.com> | Mon Aug 28 19:52:22 2023 +0000 |
committer | CQ Bot Account <flutter-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Aug 28 19:52:22 2023 +0000 |
tree | 46ca6b7e7e2c41b5369d087088c7d16f4ba07360 | |
parent | 081f6d9957141c20c5f2879cdf09f97208068f15 [diff] |
Relanding: Upload engine artifact VSAs Pull the VSA information directly from the BCID call, write it to a file, and upload it next to the provenance and artifact in GCS The first landing of this caused VSAs to overwrite the engine artifacts, so we have updated the logic to correctly write the VSAs *next* to the artifact in GCS. Change-Id: I614fd76103ffd442783a950be8b800c510f5c947 Upload vsas Change-Id: I197f2a947929454d3605864b6a354113d977ea09 Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/50160 Reviewed-by: Godofredo Contreras <godofredoc@google.com> Commit-Queue: Drew Roen <drewroen@google.com>
This repository contains Flutter's LUCI recipes. For the LUCI infrastructure config, see flutter/infra. Builds can be found in the Flutter Dashboard.
Supported repositories roll their .ci.yaml
into flutter/infra, which updates what properties builds have. For example, flutter config specifies various dependencies the different tests require, which are then used by the flutter_deps recipe_module No modifications to flutter/infra are required to work on the recipes.
Please follow instructions on Contributing docs to set up your development environment.