Allow to override the recipes cipd version.

This is needed to be able to run subbuilds using the same cipd package
as the builders. In the past subbuilds were always running from main.

Bug: https://github.com/flutter/flutter/issues/97181
Change-Id: I5c6d1a4c7217d21c5c724deadc2f6f4dded7cebe
Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/25780
Reviewed-by: Casey Hillers <chillers@google.com>
Commit-Queue: Godofredo Contreras <godofredoc@google.com>
205 files changed
tree: ae854c0db843b0b7697e6b2d3d92179d1047a0fa
  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