Reset CIPD credentials after goma is setup

Goma sets some CIPD credentials for downloading the goma package, but
doesn't reset them afterwards.  This means that subsequent uses of CIPD
which otherwise wouldn't need credentials at all attempt to use the Goma
credentials.  This doesn't cause any problems AFAIK but is still a bug
IMHO.  I found this while trying to get certain recipes running on my
local machine.

Change-Id: I5fbcca3115e798dec03cc69a73be5348c0e7e5db
Recipe-Nontrivial-Roll: build_limited_scripts_slave
Recipe-Nontrivial-Roll: release_scripts
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/build/+/1585551
Commit-Queue: Brandon Tolsch <btolsch@chromium.org>
Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
91 files changed
tree: 1249b6af88a5dfed4ad6b9d82a74407f777eb18e
  1. .gitattributes
  2. .gitignore
  3. .vpython
  4. DEPS
  5. LICENSE
  6. OWNERS
  7. PRESUBMIT.py
  8. README.md
  9. WATCHLISTS
  10. codereview.settings
  11. environment.cfg.py
  12. infra/
  13. masters/
  14. scripts/
  15. site_config/
  16. slave/
  17. tests/
  18. third_party/
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.