Roll-forward enabled_branchs tech-debt cleanup.
This re-lands 95015a6861ebe3d93ff02ef0ba50dd4b66f9e94c, with fixes around
how "enabled_branches" executes. Notably, three important bugs were fixed:
1. Read the top-level enabled_branches (was accidentally set to [])
2. Uses current branch, not the commit-origin, to filter enabled_branches.
After this change, the `{PLAT} packaging` builds that are supposed to only
be run on `beta` or `stable` channels should no longer be acidentally run
on release-candidate branches.
Change-Id: Ib616d1948506f62d303f61fa88eb44d0dc853a18
Bug: https://github.com/flutter/flutter/issues/169875
Change-Id: I578e281e7e4e46e018d07872a22c118cf1f22931
Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/66101
Commit-Queue: Matan Lurey <matanl@google.com>
Reviewed-by: John McDole <codefu@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.