[code coverage] Add revision and timestamp for each file.

For each source file in the code coverage metadata, retrieve its revision and
timestamp from the Git repository it belongs to, and add them to the file
metadata.
"git ls-files" is used to retrieve committed files in each repository, and to detect generated files.
For generated files, no such metadata is added.
Note: running "git log" on a generated file takes too long.

Bug: 922252
Change-Id: I0023d2814576a65d60462b5affda771ae4a349f9
Reviewed-on: https://chromium-review.googlesource.com/c/1419877
Auto-Submit: Shuotao Gao <stgao@chromium.org>
Reviewed-by: Yuke Liao <liaoyuke@chromium.org>
3 files changed
tree: 94e5d6dd71b7034d5b3c08383fb557abb249e054
  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.