Add a check to determine if the cache directory exists or not.

I had assumed it did since I don't think anything would run but it makes sense to check to see if it does exist or not and if not do not run the cache micro manager.

This will also simplify testing other recipe changes as you will not have to add a cache to every single recipe that touches osx_sdk currently or any other recipe that may use the cache micro manager in the future.

Test run: https://ci.chromium.org/ui/p/flutter/builders/prod.shadow/Mac%20Production%20Engine%20Drone/499/overview

Bug: Part of https://github.com/flutter/flutter/issues/141398
Change-Id: Iae4e9e97c5a7871788b8484adc72a9d636f54d16
Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/54001
Reviewed-by: Yusuf Mohsinally <mohsinally@google.com>
Reviewed-by: Keyong Han <keyonghan@google.com>
Commit-Queue: Ricardo Amador <ricardoamador@google.com>
32 files changed
tree: d6e9848d46a1628c53009622628900d22eb55d9b
  1. infra/
  2. recipe_modules/
  3. recipes/
  4. .gitignore
  5. .style.yapf
  6. AUTHORS
  7. CONTRIBUTING.md
  8. LICENSE
  9. OWNERS
  10. README.md
  11. 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.