| commit | 7afb2255290ae2681e2c2e12dbd46b47e030402e | [log] [tgz] |
|---|---|---|
| author | Nathan Mulcahey <nmulcahey@google.com> | Tue Oct 26 15:46:49 2021 +0000 |
| committer | CQ Bot Account <flutter-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Oct 26 15:46:49 2021 +0000 |
| tree | a60ee74ccb3852d46fe5b5e96400bf031efa312e | |
| parent | 85b0e70b30e908459b3f4e9b77369b34305b06de [diff] |
[auto_roller] Set Code-Review+2 The default behavior is changing, Fuchsia no longer plans to set Code-Review+2 on its rolls, so update the one usage in Flutter to set it independently. Bug: b/185545271 Change-Id: I83c9cdac87bd75a5c499e8b8a3e27e0c53972680 Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/19504 Reviewed-by: Godofredo Contreras <godofredoc@google.com> Commit-Queue: Nathan Mulcahey <nmulcahey@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