Use the builder named cache in the cros_flash recipe.

Instead of a specific one. The builder cache is already present for all
swarmbucket builds. Everything else has to be created manually. So using
the builder cache is less of a hassle, but essentially equivalent.

TBR=martiniss

Bug: 866062
Change-Id: I9018b8f64e9f240bb3dd661d1767435c439a2fb2
Reviewed-on: https://chromium-review.googlesource.com/c/1332667
Reviewed-by: Ben Pastene <bpastene@chromium.org>
Commit-Queue: Ben Pastene <bpastene@chromium.org>
3 files changed
tree: 596cf616cf4b159dfa668df6f8eb1f8b2cf11437
  1. infra/
  2. masters/
  3. scripts/
  4. site_config/
  5. slave/
  6. tests/
  7. third_party/
  8. .gitattributes
  9. .gitignore
  10. .vpython
  11. codereview.settings
  12. DEPS
  13. environment.cfg.py
  14. LICENSE
  15. OWNERS
  16. PRESUBMIT.py
  17. README.md
  18. WATCHLISTS
README.md

build

Hi build contributor! If you do any change in scripts/master/ or touching any master's html/ directories, you must restart master.chromium.fyi first and ensure that it still works before restarting other masters.

Recipes

If you're here to make a change to ‘recipes’ (the code located in scripts/slave/recipes*), please take a look at the README for more information pertaining to recipes.