Ensure that the ToT engine commit is contained within flutter/flutter candidate.

When releasing, this addition to the publish bot asserts that the commit found in flutter/flutter engine.internal file matches what is found on the same candidate branch in the engine. This is in order to validate that the commit has been rolled into the release candidate successfully.

If the commit validation fails, the release will fail at this assertion.

Bug: 289062103

Change-Id: I0da2682fdfdd1908247397ea3243227959657c97
Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/46840
Commit-Queue: Jesse Seales <jseales@google.com>
Reviewed-by: Keyong Han <keyonghan@google.com>
9 files changed
tree: 03422dd8ea34927fc62426edf96dd5f5f7181351
  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