Use the builder spec when looking up bulder GN args.

When looking up the builder GN args, there is at most one builder
involved and the operation relies only on information that is present in
the spec for that builder, so there is no need to create a bot config
object. Additionally, the _chromium_config method is only used in that
single spot and it's a small enough block of code to contain it directly
at the callsite.

Change-Id: I0da41c91b67cf4b0d7c244d5f67672ee5f9eb919
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/build/+/2795281
Auto-Submit: Garrett Beaty <gbeaty@chromium.org>
Reviewed-by: Stephen Martinis <martiniss@chromium.org>
Commit-Queue: Stephen Martinis <martiniss@chromium.org>
1 file changed
tree: c8089afdc7f7439f4f6e864f932fb34990441ef4
  1. infra/
  2. recipes/
  3. scripts/
  4. site_config/
  5. .gitattributes
  6. .gitignore
  7. .style.yapf
  8. .vpython
  9. .yapfignore
  10. codereview.settings
  11. CROS_OWNERS
  12. DEPS
  13. environment.cfg.py
  14. LICENSE
  15. OWNERS
  16. PRESUBMIT.py
  17. README.md
  18. 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.