Support for experimental runs in generic_archive

Experimental runs are running uploads to the provided path.
Instead, this change appends "experimental" to the gs_bucket such
that uploads do not affect actual used paths. Also, experimental
runs should not create .sig files.

Bug: 1166926
Change-Id: I736c40c135ae5888468277d4387d99cc6e2f0aac
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/build/+/2630488
Reviewed-by: Garrett Beaty <gbeaty@chromium.org>
Reviewed-by: Michael Moss <mmoss@chromium.org>
Commit-Queue: Jeff Yoon <jeffyoon@google.com>
2 files changed
tree: 59e2433bb280dd5c0eaf9da819013f1ef6c52b2f
  1. infra/
  2. recipes/
  3. scripts/
  4. site_config/
  5. third_party/
  6. .gitattributes
  7. .gitignore
  8. .style.yapf
  9. .vpython
  10. .yapfignore
  11. codereview.settings
  12. CROS_OWNERS
  13. DEPS
  14. environment.cfg.py
  15. LICENSE
  16. OWNERS
  17. PRESUBMIT.py
  18. README.md
  19. WATCHLISTS
README.md

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.

Style

The preferred style is PEP8 with two-space indent; that is, the Chromium Python style. Functions use lowercase_with_underscores, with the exception of the special functions RunSteps and RunTests in recipes. Use yapf (git cl format --no-clang-format) to autoformat new code.