| commit | 53ced36edd691378165ff74d7cdb0ddf0c6e2180 | [log] [tgz] |
|---|---|---|
| author | Godofredo Contreras <godofredoc@google.com> | Thu Feb 24 03:35:30 2022 +0000 |
| committer | Godofredo Contreras <godofredoc@google.com> | Thu Feb 24 03:35:30 2022 +0000 |
| tree | f5895d05c1bce4d5418de26b25010496ee7099ad | |
| parent | 5171a758eeeb5be55d6d38e1b256b1263587540b [diff] |
Change the location where font-subset file is read from. To simplify the way we generate flutter artifacts we are moving all the artifact generation logic directly to gn/ninja. In addition to that we are also modifying the path where the artifacts are generated to mimic the final destination in GCS. Bug: https://github.com/flutter/flutter/issues/81855 Change-Id: I8b9bb2a7b88817bb4ff5ff7ea9a8d8e17d45ae85 Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/27381 Reviewed-by: Dan Field <dnfield@google.com> Reviewed-by: Keyong Han <keyonghan@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