commit | 7ba72bedb60e5c63387b856e4427d17c9e3fee3b | [log] [tgz] |
---|---|---|
author | Zach Anderson <zra@google.com> | Mon Jul 29 19:01:56 2024 +0000 |
committer | CQ Bot Account <flutter-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jul 29 19:01:56 2024 +0000 |
tree | caf71538e4cfdba01cd6000c09c1456ba16a1c7d | |
parent | e3d9cae4cc7a8241346801cb6d188a12e281dbec [diff] |
Unconditionally clobber when on release candidate branches For failures like in https://ci.chromium.org/ui/p/flutter/builders/try/Linux%20Engine%20Drone/2534739/overview which likely has stale files in the tree from the future due to sharing the try bots with the main branch. Change-Id: Ie1194842bff1ded82e812fb1a775482a7b66b1d5 Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/58800 Reviewed-by: Jason Simmons <jsimmons@google.com> Commit-Queue: Zach Anderson <zra@google.com> (cherry picked from commit ee6c6a5cec8f3ebbd0a5661ab19a03831a5dc465) Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/58801 Reviewed-by: Alexander Thomas <athom@google.com>
This repository contains Flutter's LUCI recipes. For the LUCI infrastructure config, see flutter/infra. Builds can be found in the Flutter Dashboard.
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.
Please follow instructions on Contributing docs to set up your development environment.