[recipes/led_recipes_tester] Add recipe roll support.

This allows led_recipes_tester to trigger an alternate (presumably
faster) test CL for when it detects a recipes.cfg change.

Recipes work inside the build repo which affect the chromium recipes
should continue to test with the current (full) CL.

R=martiniss@chromium.org, tandrii@chromium.org

Bug: 920772
Change-Id: I8762e23e9ffa38df8d9bdae9104094ed4bc7fcbc
Reviewed-on: https://chromium-review.googlesource.com/c/1405751
Commit-Queue: Robbie Iannucci <iannucci@chromium.org>
Reviewed-by: Stephen Martinis <martiniss@chromium.org>
Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
5 files changed
tree: ff02cf5f8f2c3f169063f51926455fb5e90180b2
  1. infra/
  2. masters/
  3. scripts/
  4. site_config/
  5. slave/
  6. tests/
  7. third_party/
  8. .gitattributes
  9. .gitignore
  10. .vpython
  11. codereview.settings
  12. DEPS
  13. environment.cfg.py
  14. LICENSE
  15. OWNERS
  16. PRESUBMIT.py
  17. README.md
  18. WATCHLISTS
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.