Compute monorepo engine_v2 builder names from build config

To let the monorepo builder use the flutter/engine/ci/builders
build configurations, rather than maintaining modified copies
of them, the subbuilder names and buckets should be computed from
the flutter/engine builder configuration data.

This adds code to shard_utils_v2 recipe module to compute the
monorepo drone builder names, just as the Flutter engine drone
builder names are computed.

Bug: b/245485535
Change-Id: I670e5e9531c3f0f849b0fda78c072368086ef876
Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/44300
Reviewed-by: Godofredo Contreras <godofredoc@google.com>
Commit-Queue: William Hesse <whesse@google.com>
13 files changed
tree: 72a05fe8b261874f9bb761a53b129cb1bdc3f5ed
  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