| commit | fdc2d0f1835d9da93b315853984cc072d320332c | [log] [tgz] |
|---|---|---|
| author | Godofredo Contreras <godofredoc@google.com> | Tue Oct 26 17:42:43 2021 +0000 |
| committer | CQ Bot Account <flutter-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Oct 26 17:42:43 2021 +0000 |
| tree | 1b7a6839474ca6b07ef8847c836bbce7932fbb69 | |
| parent | 7afb2255290ae2681e2c2e12dbd46b47e030402e [diff] |
Use property branch instead of the one from buildbucket. This is to allow re-running tasks from production branches. Change-Id: I303bf44bd938c9a77bca2b8e4012b885dd230964 Bug: https://github.com/flutter/flutter/issues/92127 Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/19500 Reviewed-by: Casey Hillers <chillers@google.com> Reviewed-by: Keyong Han <keyonghan@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