Google Git
Sign in
chromium / chromium / tools / build / f0a1d71f97818db24a776e57ab77c48f59bc2830
commitf0a1d71f97818db24a776e57ab77c48f59bc2830[log] [tgz]
authorGregory Guterman <guterman@google.com>Wed Jan 20 20:18:17 2021
committerLUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Jan 20 20:18:17 2021
treeb9dacb271d4a8be752fe7a6b5a5340aedd209939
parentc9a7bfb4073085538192556370806df13f61eb4f [diff]
Refactor RTS recipe_module to use a spec object instead of separate values

As I was writing the chromium recipe integration, it felt awkward to work with all the spec variables separately. This should fix that.

Bug: 1159191
Change-Id: I57adcd3a859ef8c66a94b51bf246f89327a6bd9a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/build/+/2628307
Commit-Queue: Gregory Guterman <guterman@google.com>
Reviewed-by: Garrett Beaty <gbeaty@chromium.org>
Reviewed-by: Nodir Turakulov <nodir@chromium.org>
3 files changed
tree: b9dacb271d4a8be752fe7a6b5a5340aedd209939
  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.