|author||Godofredo Contreras <firstname.lastname@example.org>||Fri Sep 30 22:32:01 2022 +0000|
|committer||CQ Bot Account <email@example.com>||Fri Sep 30 22:32:01 2022 +0000|
Use generic drones for recipes_v2 in try. The current logic was using production/staging drones for try jobs. The recipe module has two different paths a previous CL landed the functionality for led runs and this one applies the same changes to build bucket. Bug: https://github.com/flutter/flutter/issues/112722 Change-Id: I1697c02cf32d2810cad33be243a3afea0d03db74 Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/34521 Reviewed-by: Ricardo Amador <firstname.lastname@example.org> Commit-Queue: Godofredo Contreras <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