commit: 95015a6861ebe3d93ff02ef0ba50dd4b66f9e94c
[log]
author: Matan Lurey <matanl@google.com>
Fri May 30 14:40:28 2025 -0700
committer: CQ Bot Account <flutter-scoped@luci-project-accounts.iam.gserviceaccount.com>
Fri May 30 14:40:28 2025 -0700
tree: e22356ce4c7b88d7899e368c06146436e8a5c9c8
parent: 0793952cf07fa6c3885c1f2a8f9384bd053ce6b8 [diff]

Cleanup enabled_branches tech-debt, add scheduler-release support.

There was legacy support that treated an empty enabled_branches
differently, where .ci.yaml upstream were patched to no longer
need it, which is removed in this CL.

Additionally, adds scheduler: release for release candidate build
targets, so that the field schedule_during_release_override can be
removed.

See https://github.com/flutter/flutter/issues/168913.

Change-Id: I4d0d3c4e5aaff50140cc499f1814c3a112e715ed
Bug: https://github.com/flutter/flutter/issues/168913
Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/65931
Reviewed-by: Jason Simmons <jsimmons@google.com>
Commit-Queue: Matan Lurey <matanl@google.com>

recipes/release/release_builder.expected/base_linux_main_monorepo.json[diff]
recipes/release/release_builder.expected/filter_git_ref_not_stable_or_beta_on_release_channel.json[diff]
recipes/release/release_builder.expected/linux_schedule_during_release_override.json[Renamed from recipes/release/release_builder.expected/linux_schedule_during_release_override_with_empty_enabled_branch.json - diff]
recipes/release/release_builder.expected/linux_scheduler_release.json[Renamed from recipes/release/release_builder.expected/linux_schedule_during_release_override_with_matching_enabled_branch.json - diff]
recipes/release/release_builder.expected/retry_override_still_runs_non_config_name_target.json[diff]
recipes/release/release_builder.py[diff]

6 files changed

tree: e22356ce4c7b88d7899e368c06146436e8a5c9c8

README.md

Flutter LUCI Recipes

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.

Contributing

Please follow instructions on Contributing docs to set up your development environment.