Update release tagging & pushing recipe to use gh cli and new github PAT

The previous iteration of the recipe did not use the gh cli which created failures. This recipe uses the gh cli and also pushes after authenticating with a new github PAT generated for this workflow. That new PAT is stored in GCP.

successful led run: https://luci-milo.appspot.com/raw/build/logs.chromium.org/flutter/led/jseales_google.com/033d40a2747a0873179eadb866e20329b2c3927ceef8fd547630b5fb11c2f585/+/build.proto

Change-Id: I6ad4538b887930ee22acc9d4695a0b27fb3a7389
Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/38320
Commit-Queue: Jesse Seales <jseales@google.com>
Reviewed-by: Casey Hillers <chillers@google.com>
Reviewed-by: Godofredo Contreras <godofredoc@google.com>
5 files changed
tree: 59761ea82f15d80883fa45e6b9e700e2093d5963
  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