| commit | 363a9c551c28b070aaf07c266af4b417274f53aa | [log] [tgz] |
|---|---|---|
| author | Matan Lurey <matanl@google.com> | Mon Jun 23 11:11:41 2025 -0700 |
| committer | CQ Bot Account <flutter-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jun 23 11:11:41 2025 -0700 |
| tree | 0144b3918b9a862f993d00e5fdf74a43661b8696 | |
| parent | 639606659e16c0b58e9b4107787f5ad80cb72d83 [diff] |
Continue passing is_fusion=true for release builds Release builds have branched recipes, which means that they still use the is_fusion flag to make decisions about the source tree. This has no effect on future release branches, and can be cleaned up after. Change-Id: I4345529553b12539e699244162464b6bfceaf397 Bug: https://github.com/flutter/flutter/issues/171023 Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/66900 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.