Reland "Use property branch instead of the one from buildbucket".

Context: The change was reverted because manual runs set git_ref with
the commit to be retried. This made the logic to think the commit was
coming from presubmit and the --branch flag was not setup.

This is to allow re-running tasks from production branches.

Change-Id: Ia7e23c37b90f97038b6391fcd58a84abd4580ae1
Bug: https://github.com/flutter/flutter/issues/92127
Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/19561
Reviewed-by: Casey Hillers <chillers@google.com>
Commit-Queue: Godofredo Contreras <godofredoc@google.com>
2 files changed
tree: 0767113a464d2cefe36a4ddfddb5ef03f89b3c06
  1. infra/
  2. recipe_modules/
  3. recipes/
  4. .gitignore
  5. .style.yapf
  6. AUTHORS
  7. branch_recipes.py
  8. cat
  9. LICENSE
  10. OWNERS
  11. README.md
  12. recipes.py
README.md

Flutter LUCI Recipes

This repository contains Flutter's LUCI recipes. For the LUCI infrastructure config, see flutter/infra. Actual builds can be seen at ci.chromium.org.

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.

Configuration

Tricium configurations recipes repo.

Recipe Branching for Releases

The script branch_recipes.py is used to generate new copies of the LUCI recipes for a beta release. See Recipe Branching for Releases for more information. For usage:

$ ./branch_recipes.py --help