Explicitly specify ninja path in deterministic builder.

Some builders that do not have ninja in its PATH fail to get
dependencies in compare_build_artifacts.py because it cannot execute
ninja.
This cl explicitly specify ninja path to fix the issue.

Bug: 862917
Change-Id: I7f304e9c9c97e0be56079ce38d4be329aed148a0
Reviewed-on: https://chromium-review.googlesource.com/1135882
Reviewed-by: Marc-Antoine Ruel <maruel@chromium.org>
Commit-Queue: Marc-Antoine Ruel <maruel@chromium.org>
23 files changed
tree: 77605256dbd6e477055c7a7bd659d66fbff41636
  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.