| commit | 736aac3f34634ffc45d632a7c0f6737baa152fdc | [log] [tgz] |
|---|---|---|
| author | Godofredo Contreras <godofredoc@google.com> | Thu Jan 12 01:05:29 2023 +0000 |
| committer | CQ Bot Account <flutter-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jan 12 01:05:29 2023 +0000 |
| tree | c7ca06f6ef9a150af262d7e4fcdfe6461c273d97 | |
| parent | 430623283f89d99d654780d277a66379022e5561 [diff] |
Propagate gclient_variables in buildbucket builds. The sharding utility maintains two different paths for triggering builds based on whether they are being run with led on directly in the infrastructure. In a previous CL we added propagation logic for gclient variables to led but not to buildbucket. Change-Id: I14c1b1fb80c6e5e1e2f031375afee79ae3ba0cff Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/38100 Reviewed-by: Harry Terkelsen <het@google.com> Reviewed-by: Ricardo Amador <ricardoamador@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