Roll recipe dependencies (nontrivial). This is an automated CL created by the recipe roller. This CL rolls recipe changes from upstream projects (fuchsia) into this repository. Please review the expectation changes, and LGTM+CQ. fuchsia: https://crrev.com/c5714617eee0ca6f76aa29d3ef03aafa844eddb5 (haowei@google.com) [goma] Use 'integration' ref More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug. R=chillers@google.com, fujino@google.com, godofredoc@google.com, keyonghan@google.com Recipe-Tryjob-Bypass-Reason: Autoroller Bugdroid-Send-Email: False Change-Id: I84e27441f38b587ee91b07cc3e06f80e0fa2eb10 Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/20100 Commit-Queue: flutter-prod-builder@chops-service-accounts.iam.gserviceaccount.com <flutter-prod-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: Godofredo Contreras <godofredoc@google.com> Reviewed-by: 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