tree 1b316f837780e7c3b2a3e7edd98449366088554e
parent 31afbf2c8daf3cf81aa9279d0e1b60e9c0c70132
author Drew Roen <drewroen@google.com> 1693258034 +0000
committer CQ Bot Account <flutter-scoped@luci-project-accounts.iam.gserviceaccount.com> 1693258034 +0000

Add cherrypicks for flutter bcid validation and vsa uploading

Change-Id: I699428c4d314b1de5b71924f9760d93bd120ba71


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>


Initial commit to add BCID provenance verification.

Given the restricted access to dart-internal, wrap the initial verification in a try-catch so that it is not blocking. This will allow the builder recipe to continue working while we ensure BCID verification is working correctly.

BCID verification will not be considered complete until this try-except is removed, as correctly implemented BCID verification SHOULD fail the build

Bug: b/272046059
Change-Id: I8dac50937bfe36b5462643cb7f77794885533fb6
Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/48040
Commit-Queue: Drew Roen <drewroen@google.com>
Reviewed-by: Jesse Seales <jseales@google.com>
Reviewed-by: Godofredo Contreras <godofredoc@google.com>
Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/50300