Clean all git repositories in the checkout path when building a release branch

This is part of an attempt to find a faster way to ensure a sufficiently clean source tree for release branches.

Release branch builds are currently doing a clobber of the bot caches (see https://flutter.googlesource.com/recipes/+/ee6c6a5cec8f3ebbd0a5661ab19a03831a5dc465).  It should be possible to avoid that by removing any files in the source repositories that are not tracked by Git.

For now, this PR keeps the clobber while we continue investigating any other state on the bots that may need to be cleaned.

See https://github.com/flutter/flutter/issues/169887

Change-Id: I8ef7865bf5273fcc89513bd056c7451bcf973e59
Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/66103
Reviewed-by: Matan Lurey <matanl@google.com>
Commit-Queue: Jason Simmons <jsimmons@google.com>
11 files changed
tree: 58fbc4639c7f7a8e3efd66b1006b6e179b4c56e6
  1. .vscode/
  2. infra/
  3. recipe_modules/
  4. recipes/
  5. .gitignore
  6. .style.yapf
  7. AUTHORS
  8. CONTRIBUTING.md
  9. LICENSE
  10. OWNERS
  11. README.md
  12. recipes.py
README.md

Flutter LUCI Recipes

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.

Contributing

Please follow instructions on Contributing docs to set up your development environment.