| commit | 8549c558670d247ad35b27dc6b7e92a14eed1a52 | [log] [tgz] |
|---|---|---|
| author | Godofredo Contreras <godofredoc@google.com> | Fri Jan 21 00:33:32 2022 +0000 |
| committer | CQ Bot Account <flutter-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jan 21 00:33:32 2022 +0000 |
| tree | fb1be89b73c2a004a2f1abb33b1d85373bd87080 | |
| parent | 43e9b35f39ade8ad886ab06ef60053ce57f1ad4d [diff] |
Add revision to the codesing validation. Because the conductor codesign validation was not getting a commit it was trying to checkout the ToT commit from master making the test fail because the binaries were not signed yet. Bug: https://github.com/flutter/flutter/issues/96956 Bug: https://github.com/flutter/flutter/issues/96889 Change-Id: Ied5adfaa77d4bf17ecfd618225dcc564da52bc7c Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/25602 Reviewed-by: Christopher Fujino <fujino@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