[Open Screen] Migrate GCC builders to local build

Currently, Open Screen gcc builders use the legacy Goma backend, which
is being turned down next month. This patch updates the openscreen.py
recipe script to check if the is_gcc argument is passed, then builds
using the new Goma backend or locally on the bot as appropriate.

Bug: b/168701898
Change-Id: Ib25b1dccbf5ece20853a1625d47a5da5656d4ad0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/build/+/2414508
Commit-Queue: Jordan Bayles <jophba@chromium.org>
Reviewed-by: Brandon Tolsch <btolsch@chromium.org>
2 files changed
tree: de305a964df1815fd2f865e1eff747b8e6acd12c
  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.