commit | 45441df105a207118b130a7644dc87996ceb7885 | [log] [tgz] |
---|---|---|
author | Godofredo Contreras <godofredoc@google.com> | Fri Aug 13 21:44:06 2021 +0000 |
committer | CQ Bot Account <flutter-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Aug 13 21:44:06 2021 +0000 |
tree | b1e65f436a255ea0b8b66d03eab6bebf562488bd | |
parent | 2291176af95721d9bbe98133f7c42415b38edb63 [diff] |
Add support for isolate archives in engine_v2. Engine_v2 recipes will be archiving artifacts to reuse across different subbuilds. Change-Id: I18dac919901a1055ad7698b256aa57b27a890143 Bug: https://github.com/flutter/flutter/issues/81855 Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/16901 Reviewed-by: Yegor Jbanov <yjbanov@google.com> Reviewed-by: Keyong Han <keyonghan@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