| commit | b19888c7da10522dd64e5b6f41fa78adfe0d7240 | [log] [tgz] |
|---|---|---|
| author | Godofredo Contreras <godofredoc@google.com> | Mon Jan 24 21:12:59 2022 +0000 |
| committer | CQ Bot Account <flutter-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jan 24 21:12:59 2022 +0000 |
| tree | de7986904dfb6fc87294de9ec781fe5503da3428 | |
| parent | cfd37c576a84950565c5d997338dae1cea92fe75 [diff] |
Guess the branch for the current stable | beta commit. On release branches we don't know the branch name the commit is coming from. In some cases knowing the source branch is required to reliably use the correct versions of dependent repositories to use. An example of this is engine builds checking out framework, framework checking out plugins or adhoc tests checking out the correct versions of the code. Bug: https://github.com/flutter/flutter/issues/94948 Bug: https://github.com/flutter/flutter/issues/94949 Bug: https://github.com/flutter/flutter/issues/91921 Change-Id: Ide053d33f330871515c04c9aa544a25c178e87bd Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/25660 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