Move firebaselab configs to ci.yaml.

The current implementation forces to update recipes to
add/remove/updated physical or virtual devices from firebaselab tests.
This forces a monolithic tests running all the configurations and
removes the ability to move some configs to bringup.

This change moves the configurations to properties that can be passed
from .ci.yaml. It will allow to split the monolithic test as multiple
builds that can be marked as bringup independently.

Bug: https://github.com/flutter/flutter/issues/127884
Bug: https://github.com/flutter/flutter/issues/118736
Change-Id: I063ce80c7936bfa00fa14473cd253ac4ae46fd89
Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/45182
Commit-Queue: Godofredo Contreras <godofredoc@google.com>
Reviewed-by: Reid Baker <reidbaker@google.com>
1 file changed
tree: d6897a726e17ce8d9da0f882cf488657493b0484
  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