| commit | 89d11694fce4209282b4b1a9dad769011b983b6a | [log] [tgz] |
|---|---|---|
| author | Godofredo Contreras <godofredoc@google.com> | Thu Feb 03 22:53:16 2022 +0000 |
| committer | CQ Bot Account <flutter-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Feb 03 22:53:16 2022 +0000 |
| tree | e8544c5c1c445a57c5e07d2121c9777234a652a6 | |
| parent | 25483898815ed63f8142914a9686208998f0a5d5 [diff] |
Validate if current commit is in release and main branches. This method will be used to skip build executions in release branches when the build has already run on main. Bug: https://github.com/flutter/flutter/issues/64577 Change-Id: Ieee07ca3413bf14a241aeb47e4f0aae2a72079a1 Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/26100 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