Workaround for dirty goma deps_cache

Goma version 132 changed the cache items, but the goma roll was
reverted. Using version 132 items in version 131 is not good.

TBR: phajdan.jr@chromium.org
Bug: 737896
Change-Id: I353d6b9f841e7e9d4b7eb5ee810edc3c9ae3351e
Reviewed-on: https://chromium-review.googlesource.com/555050
Reviewed-by: Shinya Kawanaka <shinyak@chromium.org>
Reviewed-by: Paweł Hajdan Jr. <phajdan.jr@chromium.org>
Commit-Queue: Shinya Kawanaka <shinyak@chromium.org>
532 files changed
tree: c16da5f96fa2c0b6648ffad6b6670a6bdbf9d8d9
  1. infra/
  2. masters/
  3. scripts/
  4. site_config/
  5. slave/
  6. tests/
  7. third_party/
  8. .gitattributes
  9. .gitignore
  10. codereview.settings
  11. DEPS
  12. environment.cfg.py
  13. LICENSE
  14. OWNERS
  15. PRESUBMIT.py
  16. README.md
  17. 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.