Use generic drones for recipes_v2 in try.

The current logic was using production/staging drones for try jobs. The
recipe module has two different paths a previous CL landed the
functionality for led runs and this one applies the same changes to
build bucket.

Bug: https://github.com/flutter/flutter/issues/112722
Change-Id: I1697c02cf32d2810cad33be243a3afea0d03db74
Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/34521
Reviewed-by: Ricardo Amador <ricardoamador@google.com>
Commit-Queue: Godofredo Contreras <godofredoc@google.com>
6 files changed
tree: dd93ef8275117fef9ed78fb64f72bed289e4b029
  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