| commit | 9855bacbba60e2b8ffdb60ca5b0e0e946b9da3c4 | [log] [tgz] |
|---|---|---|
| author | recipe-roller <flutter-prod-builder@chops-service-accounts.iam.gserviceaccount.com> | Wed Feb 05 06:41:45 2025 -0800 |
| committer | CQ Bot Account <flutter-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Feb 05 06:41:45 2025 -0800 |
| tree | bb35353a4a8006a92b22818e2057f1a6ec57f197 | |
| parent | b6342db82a11a91eb848c6d739385d16cfb2b410 [diff] |
Roll recipe dependencies (nontrivial). This is an automated CL created by the recipe roller. This CL rolls recipe changes from upstream projects (recipe_engine) into this repository. The build that created this CL was https://ci.chromium.org/b/8723771286387955553 Please review the expectation changes, and LGTM+CQ. recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py.git/+/0d8a28f1756fca05c9f252a9968b7b11822c8558 0d8a28f (mohrr@google.com) [cipd] Add build_id metadata to pkg-register calls Please check the following references for more information: - autoroller, https://chromium.googlesource.com/infra/luci/recipes-py/+/main/doc/workflow.md#autoroller - rollback, https://chromium.googlesource.com/infra/luci/recipes-py/+/main/doc/workflow.md#rollback - cross-repo dependencies, https://chromium.googlesource.com/infra/luci/recipes-py/+/main/doc/cross_repo.md Use https://goo.gl/noib3a to file a bug. R=flutter-infra@grotations.appspotmail.com, fujino@google.com, zra@google.com Recipe-Tryjob-Bypass-Reason: Autoroller Ignore-Freeze: Autoroller Bugdroid-Send-Email: False Change-Id: Ie71c521baa046569b6e1c2f9c7512673974cdedb Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/62920 Reviewed-by: Zach Anderson <zra@google.com> Commit-Queue: Zach Anderson <zra@google.com>
This repository contains Flutter's LUCI recipes. For the LUCI infrastructure config, see flutter/infra. Builds can be found in the Flutter Dashboard.
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.
Please follow instructions on Contributing docs to set up your development environment.