Patch recipe to use git_branch to decide on uploading metrics.

The current logic always tries to upload metrics because the properties
used to validate the branch are populated only on luci-scheduler builds.

Change-Id: Ia122940ed985cc8d2ad5e6e47f211e5d4b939bcf
Bug: https://github.com/flutter/flutter/issues/92127
Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/19322
Reviewed-by: Keyong Han <keyonghan@google.com>
Commit-Queue: Godofredo Contreras <godofredoc@google.com>
1 file changed
tree: 5cb6f7a1d2cf91a33ea2ba949c5e904de71693a5
  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