[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. .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.