|author||Godofredo Contreras <firstname.lastname@example.org>||Wed Feb 16 01:25:01 2022 +0000|
|committer||CQ Bot Account <email@example.com>||Wed Feb 16 01:25:01 2022 +0000|
Duplicate engine and packaging recipes. This is in preparation to move organize the recipes in folders aligned with the repository where they are being used. We need to do this in three steps to avoid breaking the devlopement workflows: 1.- Duplicate the recipes in the target location 2.- Change .ci.yaml to point to recipes in the new location. 3.- Delete recipes from the source location Bug: https://github.com/flutter/flutter/issues/97735 Change-Id: I10799fdeb89532fa5974aaa8aed5a74dce1892e3 Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/27101 Reviewed-by: Yusuf Mohsinally <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.
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