| commit | 23557c4a6e192e02bbed24fa972381d68d626d08 | [log] [tgz] |
|---|---|---|
| author | Stuart Morgan <stuartmorgan@google.com> | Fri Sep 03 19:38:26 2021 +0000 |
| committer | CQ Bot Account <flutter-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Sep 03 19:38:26 2021 +0000 |
| tree | 076194c3827c0e352111307ea91d472a23f31547 | |
| parent | d5cbcbb8607eca1932949994186fa79997fbc8f0 [diff] |
Make the plugin recipe generic Instead of running a set of test steps defined in the recipe, read them from files in the flutter/plugins repository. Bug: https://github.com/flutter/flutter/issues/89373 Change-Id: Icf4dd75dedce3fe0e8e04c8153c60c663cff58e7 Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/17645 Reviewed-by: Casey Hillers <chillers@google.com> Commit-Queue: Stuart Morgan <stuartmorgan@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