commit | 6925bb7fc429930570d86ea2b0f68cb787ad376a | [log] [tgz] |
---|---|---|
author | Jesse Seales <jseales@google.com> | Fri Jan 27 19:24:20 2023 +0000 |
committer | CQ Bot Account <flutter-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jan 27 19:24:20 2023 +0000 |
tree | b1ae0098d257c7fadd6ab1f72e36e66f3df80926 | |
parent | 73484754463a44d55764696346b5dbb03c558e77 [diff] |
Add release publish recipe In an effort to match SLSA requirements on release workflows, moving some release logic into a recipe will allow for the logic to be triggered by tool_proxy and run on dart-internal SLSA compliant builders. Bug: b/265318414 Change-Id: I1b145d5a32a97e4c40eec62c2f849df75b27d937 Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/38134 Commit-Queue: Jesse Seales <jseales@google.com> Reviewed-by: Casey Hillers <chillers@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.
Running python recipes.py test train
will execute all of the tests in this repository
Required binary is not found on PATH: cipd
when testing locallyYou need to ensure depot_tools is installed. See Depot Tools Installation Tutorial