| commit | ececcc01c0e638a392f984a30dd7473ef47948bf | [log] [tgz] |
|---|---|---|
| author | Keyong Han <keyonghan@google.com> | Fri Sep 17 16:24:53 2021 +0000 |
| committer | CQ Bot Account <flutter-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Sep 17 16:24:53 2021 +0000 |
| tree | 7229bc875ca5c2a8c95931d3f99f7fdb99b704e3 | |
| parent | 8af25d4ba32b3ad90c4e698d65dc70a91d5c604f [diff] |
Append "test" key word in engine test steps Existing test steps use random step names for different tests/recipes. This CL consolidates all test steps with prefix `test`, so that we can send notification consistently for all. Change-Id: I8f6bcbdb7116307919317094ba704792b165eba4 Bug: https://github.com/flutter/flutter/issues/89308 Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/18160 Reviewed-by: Godofredo Contreras <godofredoc@google.com> Commit-Queue: 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