Create a no-op step to set the target_buildername property on.

Currently, the target_buildername property is being set on the step
result retrieved via step.active_result, but this relies on whatever
code was last executed leaving an open step, which unnecessarily
constrains the implementation of the called code.

Change-Id: Ia95813d5c2e0f13d31072919d609065e87bea72d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/build/+/2454508
Auto-Submit: Garrett Beaty <gbeaty@chromium.org>
Reviewed-by: Stephen Martinis <martiniss@chromium.org>
Commit-Queue: Stephen Martinis <martiniss@chromium.org>
28 files changed
tree: 98a3b3a1b4a61298b8fb647785c40f6cd5908350
  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.