|author||Jenn Magder <email@example.com>||Fri Aug 26 01:49:26 2022 +0000|
|committer||CQ Bot Account <firstname.lastname@example.org>||Fri Aug 26 01:49:26 2022 +0000|
Build ios-deploy for arm64 and x86_64. Tested this locally by building and copying into Flutter cache. ``` ios-deploy/ios-deploy: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit executable x86_64 - Mach-O 64-bit executable x86_64] [arm64:Mach-O 64-bit executable arm64 - Mach-O 64-bit executable arm64] ios-deploy/ios-deploy (for architecture x86_64): Mach-O 64-bit executable x86_64 ios-deploy/ios-deploy (for architecture arm64): Mach-O 64-bit executable arm6 ``` Bug: https://github.com/flutter/flutter/issues/69157 Change-Id: I8ae59141a5fb0f9183bab4d66bed5c9191676a1b Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/32932 Commit-Queue: Jenn Magder <email@example.com> Reviewed-by: Keyong Han <firstname.lastname@example.org> Reviewed-by: Christopher Fujino <email@example.com>
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.
Tricium configurations recipes repo.
python recipes.py test train will execute all of the tests in this repository