[gatekeeper] Simplify chromium.perf config

The chromium.perf config duplicates a lot of configuration, and names
a half dozen bots whose names changed long ago. This CL simplifies it
to simply care about the same steps that normal chromium CI builders
care about. This also fixes the config file to be fully loadable by
gatekeeper_ng_config.py.

Bug: 944666
Change-Id: I00593f0782a9d0cb80a4977dfe6df35b202a65e1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/build/+/1535709
Auto-Submit: Aaron Gable <agable@chromium.org>
Reviewed-by: Sean McCullough <seanmccullough@chromium.org>
Commit-Queue: Aaron Gable <agable@chromium.org>
1 file changed
tree: d3cb5d3b728cda9857e91bca5d52c04ba0d8a39f
  1. .gitattributes
  2. .gitignore
  3. .vpython
  4. DEPS
  5. LICENSE
  6. OWNERS
  7. PRESUBMIT.py
  8. README.md
  9. WATCHLISTS
  10. codereview.settings
  11. environment.cfg.py
  12. infra/
  13. masters/
  14. scripts/
  15. site_config/
  16. slave/
  17. tests/
  18. third_party/
README.md

build

Hi build contributor! If you do any change in scripts/master/ or touching any master's html/ directories, you must restart master.chromium.fyi first and ensure that it still works before restarting other masters.

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.