Move recipe config source_side_spec_dir from chromium_tests to chromium.

This is so the value can be accessed by one of chromium_test's
dependent modules (ie: filter).

ios-sim run: https://ci.chromium.org/swarming/task/44dbdb44c9441a10
mac-rel run: https://ci.chromium.org/swarming/task/44dbdb9478392e10

Prep'ed downstream roll at:
crrev.com/i/1311443

Recipe-Manual-Change: build_limited_scripts_slave
Bug: 960917
Change-Id: Id12ae2b53837a16e001d06f64872286f5785328d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/build/+/1614432
Reviewed-by: Stephen Martinis <martiniss@chromium.org>
Commit-Queue: Ben Pastene <bpastene@chromium.org>
72 files changed
tree: 1efb91f2db23c7b72de02a6dd4b4ff5891ada1f4
  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.