Use recipes from corresponding release candidate branch.

This is to ensure builders are using branched out versions of recipes.

Bug: https://github.com/flutter/flutter/issues/128079
Change-Id: Ic2c079de7c12712139e488ea6c58a3a254617f49
Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/45321
Commit-Queue: Godofredo Contreras <godofredoc@google.com>
Reviewed-by: Jesse Seales <jseales@google.com>
Reviewed-by: Drew Roen <drewroen@google.com>
(cherry picked from commit 32bf5af4857768f17e36add4e41c58f774557c31)
Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/45360
3 files changed
tree: f2104297acae2794def89b2d7bead98bd9a6ea19
  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