Use the bucket to determine if builds are from release candidate.

Currently we rely on the git_branch property being passed from the
scheduler that is not available in dart internal. If the property is not
there we fallback to use the bucket to find if we are in a release
candidate branch.

Change-Id: Ia26521b830546d09b6e304a828939715ffec9f4d
Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/44740
Reviewed-by: Drew Roen <drewroen@google.com>
Commit-Queue: Godofredo Contreras <godofredoc@google.com>
68 files changed
tree: 1e7d6db979d4d2ccc3ca2fb8880b192a6367f0b4
  1. infra/
  2. recipe_modules/
  3. recipes/
  4. .gitignore
  5. .style.yapf
  6. AUTHORS
  7. LICENSE
  8. OWNERS
  9. README.md
  10. 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.

Testing locally

Running python recipes.py test train will execute all of the tests in this repository

Troubleshooting

Required binary is not found on PATH: cipd when testing locally

You need to ensure depot_tools is installed. See Depot Tools Installation Tutorial