commit | 7477177c6af7e88f9edc54dd802d967fffb8bf63 | [log] [tgz] |
---|---|---|
author | Godofredo Contreras <godofredoc@google.com> | Wed Oct 27 20:43:49 2021 +0000 |
committer | CQ Bot Account <flutter-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Oct 27 20:43:49 2021 +0000 |
tree | 0767113a464d2cefe36a4ddfddb5ef03f89b3c06 | |
parent | 95f5d37134887ceaccbdf708e2840dcdea2bfa24 [diff] |
Reland "Use property branch instead of the one from buildbucket". Context: The change was reverted because manual runs set git_ref with the commit to be retried. This made the logic to think the commit was coming from presubmit and the --branch flag was not setup. This is to allow re-running tasks from production branches. Change-Id: Ia7e23c37b90f97038b6391fcd58a84abd4580ae1 Bug: https://github.com/flutter/flutter/issues/92127 Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/19561 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