Checkout commit for customer_testing

The `GIT_BRANCH` is `master` for both pre-submit and post-submit. This is okay for post-submit as we are validating TOT, but it fails to validate PR changes for pre-submit. This CL does
1) Checkouts latest commit instead of branch `master`
2) No-op for release branches

Led runs:
pre-submit (based on PR: https://github.com/flutter/flutter/pull/105166): https://ci.chromium.org/raw/build/logs.chromium.org/flutter/led/keyonghan_google.com/325a7fdf36bc45bb903343dcceb5ed08a77e7c46b86a1b00fbb72bcd0a63f4de/+/build.proto?server=chromium-swarm.appspot.com
post-submit: https://ci.chromium.org/raw/build/logs.chromium.org/flutter/led/keyonghan_google.com/be52a8d72e863ee18c54a465d9d51e2bfa43f24ee8a95adf1b8242b8a5a311c6/+/build.proto?server=chromium-swarm.appspot.com
Change-Id: Iecea93d5ce5028ba2774fef989b7839a77a27da6
Bug: https://github.com/flutter/flutter/issues/104433
Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/30840
Reviewed-by: Christopher Fujino <fujino@google.com>
Commit-Queue: Keyong Han <keyonghan@google.com>
128 files changed
tree: 22ec3fe192b66e29d6f35fa682cfaa686be14163
  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