godofredoc
godofredoc
There should be only a single top level build triggering mac and mac_arm64 release builders.
Until bcid tooling is available for windows bcid stage reporting should be skipped.
Drone dimensions were passed as properties when the sharding utility is expecting them in the target. Bug: https://github.com/flutter/flutter/issues/116794 ## Pre-launch Checklist - [X] I read the [Contributor Guide] and followed...
The builder names are not consistent with the packaging or flutter framework builders. In addition to that we should also move the engine release builders to run only on release...
``` The recipe has crashed at point 'Uncaught exception'! Traceback (most recent call last): File "C:\b\s\w\ir\kitchen-checkout\recipe_engine\recipe_engine\internal\engine.py", line 585, in run_steps raw_result = recipe_obj.run_steps(api, engine) File "C:\b\s\w\ir\kitchen-checkout\recipe_engine\recipe_engine\internal\recipe_deps.py", line 931, in run_steps...
Back in Aug 2022 when we worked on SLSA compliance for the cocoon repository we where missing the policy verification. Since then the Google Cloud and SLSA teams have collaborated...
The following is the list of things to solve with a refactoring of the xcode tooling, modules and recipes: - [x] Consolidate different xcode named caches into one `flutter_xcode` with...
E.g provenance files for `gs://flutter_archives_v2/flutter_infra_release/flutter/c76035429c3695a2e4920017be754beab59c720c//flutter_patched_sdk.zip` are uploaded as `gs://flutter_archives_v2/flutter_infra_release/flutter/c76035429c3695a2e4920017be754beab59c720c//flutter_patched_sdk.zip.intoto.jsonl` and `gs://flutter_archives_v2/flutter_infra_release/flutter/c76035429c3695a2e4920017be754beab59c720c//flutter_patched_sdk.zip.provenance`
There are several builds that do not use orchestrators but that still can reuse the build configurations. Enabling the use of the builder directly will allow to reuse the recipe...