| commit | fd067364c1ff9f2a7c29c30b77aeb8dedbb6e6d0 | [log] [tgz] |
|---|---|---|
| author | Jason Simmons <jsimmons@google.com> | Thu Jun 26 12:05:13 2025 -0700 |
| committer | CQ Bot Account <flutter-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jun 26 12:05:13 2025 -0700 |
| tree | ebe26e771c9cb406ee0a368da29fc14319188db7 | |
| parent | 22ff2949949c35c18dc6c0c517405050e456bcab [diff] |
Do a git clean of all repositories in the builder cache when building a release branch This should leave the repositories in a clean state while avoiding the cost of clobbering the entire cache and downloading the repositories. The cache may be in a state where it can not run the gclient command and execute the git clean. If that happens, then fall back to clobbering the cache. See https://github.com/flutter/flutter/issues/170071 Change-Id: I35d9c2b6ef532c7032c27e00d989f43e6738e6ec Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/66360 Reviewed-by: Matan Lurey <matanl@google.com> Commit-Queue: Jason Simmons <jsimmons@google.com> Reviewed-by: John McDole <codefu@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.