| commit | d79b04799aae9ab60e5e87ecdc3f81ae6c1896e8 | [log] [tgz] |
|---|---|---|
| author | Matan Lurey <matanl@google.com> | Thu May 15 07:06:19 2025 -0700 |
| committer | CQ Bot Account <flutter-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu May 15 07:06:19 2025 -0700 |
| tree | a64145c6e1bbeaaa3f317d506a2dd691918dff02 | |
| parent | 2c1d5fcbc8882a20c4357eb01de08278d77fe8eb [diff] |
Fix schedule_during_release_override, refactor, better tests.
The bug is that the new flag, `schedule_during_release_override`, was
being evaluated in the wrong branch ("release_channel", i.e.
beta/stable, instead of "release_candidate", i.e.
"flutter-1.23-candidate.0").
While investigating I found the tests were not sufficient to catch we
were not scheduling any framework-originated release builds, so I made a
few changes to make that caught by future tests and more obvious in the
LUCI output.
Change-Id: I85a1eb40300d79f1cfbf160da98216669de64db3
Bug: https://github.com/flutter/flutter/issues/168709
Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/65400
Reviewed-by: Chris Bracken <cbracken@google.com>
Commit-Queue: Matan Lurey <matanl@google.com>
Reviewed-by: Jonah Williams <jonahwilliams@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.