| commit | 8ccfb8e3cb694df4ecbb6ca3458e2d45ec489cf1 | [log] [tgz] |
|---|---|---|
| author | Godofredo Contreras <godofredoc@google.com> | Wed Oct 19 19:31:02 2022 +0000 |
| committer | CQ Bot Account <flutter-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Oct 19 19:31:02 2022 +0000 |
| tree | 015b5c99d8ec9ffb43895075ac9515ad067145c2 | |
| parent | e02f2b41ba98db6d230fee81689e4a6e89526453 [diff] |
Fork recipes testing. This is a prerequisite to get properties injected to buildbucket api correctly. This is forked from fuchsia/recipes/recipe_modules/recipe_testing. It does not contain any changes yet but the idea is that we will be calling get-build instead of get-builder to ensure all the properties are populated. A future use case if to grab builders from release branches builds when the led recipes tests are running on release candidate branch cherry picks. Bug: https://github.com/flutter/flutter/issues/113611 Change-Id: Ie7453aa5d0c0785ef3d28b7c2a7c9103f2ae562a Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/34920 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.
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