Update engine v2 archives api.

This changes allow to upload to different buckets and paths based using
monorepo logic, buildbucket buckets and a realm from the configuration
file.

This change will allow to test artifacts and migrate to engine v2 builds
using a single change to ci.yaml and build configuration files.

label:Bot-Commit=+1
Change-Id: I32e2cb747088a5cf11b8dde7fec2525c4fef7f04
Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/39680
Tested-by: Godofredo Contreras <godofredoc@google.com>
Reviewed-by: Yusuf Mohsinally <mohsinally@google.com>
Reviewed-by: Ricardo Amador <ricardoamador@google.com>
Commit-Queue: Godofredo Contreras <godofredoc@google.com>
19 files changed
tree: 1a19b83ebba94146de99ad0b6ab05a3c6003df07
  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