| commit | b27b3cdea570b832d366920fc21841a8575efe59 | [log] [tgz] |
|---|---|---|
| author | Godofredo Contreras <godofredoc@google.com> | Wed Oct 27 23:56:10 2021 +0000 |
| committer | CQ Bot Account <flutter-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Oct 27 23:56:10 2021 +0000 |
| tree | 748ae049c3936d2069b0b25791c58c54f68332cc | |
| parent | 43c9d91da40610ff3ddfbcf91ad009517090d64f [diff] |
Propagate recipes changes to release recipes. A change to not try to upload benchmarks when re-running builds in release branches has been submitted and tested. This change is replicating that change on release recipes. Change-Id: I6fd45ea9541a62081d6c4100a17ec8ee1865e38f Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/19582 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