Check that |workspace| is not a sub-directory of an Android tree, so
that we don't `repo init` to a directory outside of |workspace|.
Test: mkdir /tmp/test && cd /tmp/test && repo init [AOSP]
Test: ./repo_diff_android.py # Should fail to repo-init
Test: rm -rf .repo/ && ./repo_diff_android.py # Should success
Change-Id: I3e1b94e8e3664cc50ab790aaa7e27b2a8d3feef0
Some old SHA1 might be invalid when we use this tool.
Ignore these projects and keep going on.
Test: run the script against an old release
Change-Id: I5c89911759de6d122052e841eef0b016fa8b1422
We are using this tools on multiple releases (tags).
Create subfolders using release names, so that results won't be
overwitten.
Test: run the script against multiple releases
Change-Id: I9a94940d630874a5b378431f20a6c1182cf11509
Add a document explaining how to create a data studio dashboard using
the repo diff tool.
Renamed repo_diff_downstream.py to repo_diff_trees.py.
Renamed exclusions.txt to android_exclusions.txt.
Not all Android source trees support build IDs and tags.
When no build tag is requested, rather than try to match
the build IDs just sync the branch tips of the upstream
and downstream source trees.
Also select two Android Oreo release candidates
as the default branches. The fact that there are frozen
branches and that the diff is small serve as a good showcase
of the tool.
Change-Id: Ifdefd79fb6b32c6b83e0aee390dd5a435b6a61fc
These tools help compare android repo workspaces for high level
analysis.
Test: Run python repo_diff/repo_diff_android.py
Change-Id: I645351521c7f61735d3ce65a93569983cd28851c
