[monorepo] Build and test monorepo builds with a custom engine version

The engine version for a monorepo build is not the flutter/engine commit
hash, but the monorepo commit hash. Use this value for the gn argument
engine_version when building and testing monorepo engine builds.

Bug: https://github.com/flutter/flutter/issues/129178
Bug: b/231927187
Change-Id: Icabdd253d0b98a3fd2ffbcde12120bf4222d32b9
Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/46300
Reviewed-by: Keyong Han <keyonghan@google.com>
Commit-Queue: William Hesse <whesse@google.com>
16 files changed
tree: b2ae44c9a2b9d8e1a13aedb3f04e39ce42501a8b
  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