Add plugin recipe support for pinned versions

flutter/plugins is moving to using a pinned version of Flutter with an
auto-roller instead of whatever the latest on a given branch is. This
defaults to the old behavior for compatibility, but allows for setting
a pinned version file in the configuration properties.

Bug: https://github.com/flutter/flutter/issues/93811
Change-Id: Ie4ba8e385ff34bc42cbd6b1842ca9de53a50eb9b
Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/25361
Reviewed-by: Godofredo Contreras <godofredoc@google.com>
Commit-Queue: Stuart Morgan <stuartmorgan@google.com>
3 files changed
tree: 65f01aed85f5fe2942087375a4075e188b3b819e
  1. infra/
  2. recipe_modules/
  3. recipes/
  4. .gitignore
  5. .style.yapf
  6. AUTHORS
  7. branch_recipes.py
  8. LICENSE
  9. OWNERS
  10. README.md
  11. 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