| commit | c6f1c3c6136e39bee643b7d600e7f38936c511bb | [log] [tgz] |
|---|---|---|
| author | Godofredo Contreras <godofredoc@google.com> | Tue Feb 22 21:47:37 2022 +0000 |
| committer | CQ Bot Account <flutter-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Feb 22 21:47:37 2022 +0000 |
| tree | 7838da391c9cae3bb1204b361be1b82b7b5ae846 | |
| parent | 081df105d447ef9c3ac5c2a091dcaafdc26d298f [diff] |
Remove duplicated recipes. Engine recipes where moved to an engine folder and a copy was left in the original location to avoid breakages. Now that all the builders are using recipes from the new location we can remove the old copies. Change-Id: I497920b0f06c553cf1443655b2945eb33bcd40e3 Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/27281 Reviewed-by: Casey Hillers <chillers@google.com> Commit-Queue: Godofredo Contreras <godofredoc@google.com>
This repository contains Flutter's LUCI recipes. For the LUCI infrastructure config, see flutter/infra. Actual builds can be seen at ci.chromium.org.
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.
The script 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