|author||Godofredo Contreras <firstname.lastname@example.org>||Wed Feb 16 02:03:31 2022 +0000|
|committer||CQ Bot Account <email@example.com>||Wed Feb 16 02:03:31 2022 +0000|
Support running recipes tests on branches different than main. This is because now we are branching out recipes for release branches and we want to run tests whenever we are cherry picking changes. Change-Id: I3d740b3a085e52599733273afa898953b66c1bd1 Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/26580 Reviewed-by: Keyong Han <firstname.lastname@example.org> Commit-Queue: Godofredo Contreras <email@example.com> Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/27102
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.
branch_recipes.py is used to generate new copies of the LUCI recipes for a beta release. See Recipe Branching for Releases for more information. For usage:
$ ./branch_recipes.py --help