Use dry run flag in recipe to avoid accidental tag push

The dry run tag will be passed from the tool-proxy invocation. The value should be True/False, and if not provided will default to True in order to protect accidental tag pushing.

Led run showing success up until dry-run creates failure at git push https://chromium-swarm.appspot.com/task?id=60c1847e7dfe0410


Bug: b/270144322

Change-Id: Id92f7110680fbfe238610f8cc5a9e9462a789910
Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/39860
Commit-Queue: Jesse Seales <jseales@google.com>
Reviewed-by: Drew Roen <drewroen@google.com>
Reviewed-by: Godofredo Contreras <godofredoc@google.com>
1 file changed
tree: 1c5634da6db09f87357e288538644c4e821645c2
  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