Add a flaky step for engine builders

This makes it easy to identify flakiness from luci build detailed page, and to collect flaky statistics and present in a dashboard. Additionally, we can also use this to trigger a notification when a flake happens.

This cl also moves the flaky_step function to the test module, so that all recipes can share.

Change-Id: I1ca6f43f39c7115f139e108981159ec0c0aa8954
Bug: https://github.com/flutter/flutter/issues/89308
Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/18341
Reviewed-by: Zach Anderson <zra@google.com>
Reviewed-by: Godofredo Contreras <godofredoc@google.com>
Commit-Queue: Keyong Han <keyonghan@google.com>
14 files changed
tree: 45e7f07cba5e29c9d09248f0765cfea4ff6f7612
  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