commit | cec1da8c4379bdc57ad7e1aabada019604d54966 | [log] [tgz] |
---|---|---|
author | Matan Lurey <matanl@google.com> | Wed Jun 25 13:58:58 2025 -0700 |
committer | CQ Bot Account <flutter-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jun 25 13:58:58 2025 -0700 |
tree | 192222c30934aac50d5628a8547288a2cbfa6415 | |
parent | 59ab254cde2ad7c114256fde569d226c2b470dee [diff] |
Migrate how flutter/docs determines a release branch. General cleanup after https://github.com/flutter/flutter/issues/171045; we don't want to have multiple ways of determining a release branch across the recipes codebase. Change-Id: If8536e2826e88d3d07c46b49a5f8796602995850 Bug: https://github.com/flutter/flutter/issues/171045 Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/67100 Reviewed-by: Jason Simmons <jsimmons@google.com> Commit-Queue: Matan Lurey <matanl@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.