[monorepo] Upload engine artifacts from monorepo try job engine builds

The artifacts from engine builds of a monorepo try job are uploaded
to a new bucket flutter_monorepo_try_artifacts. The engine version
used as a path to the artifact location is the buildbucket ID of the
engine_v2 try builder, which is passed to subbuilds as a try_build_identifier
property.

Bug: b/259512595
Change-Id: Iabe44ed6218c5f01571d978e3d08a2042eca12ee
Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/45220
Reviewed-by: Keyong Han <keyonghan@google.com>
Commit-Queue: William Hesse <whesse@google.com>
24 files changed
tree: c5d75102cc6f463580c252912ec94b58700ff647
  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