-
Notifications
You must be signed in to change notification settings - Fork 69
Add --fineGrainedHashExternalRepos #174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This flag makes bazel-diff generate fine-grained hash for the explicitly mentioned external repos. This way, bazel-diff is smarter when handling external repos like `@maven` in a monorepo setting.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Really like the approach! Minor comments
@tgeng I am sorry, I am now realizing that |
Np! Pushed another patch. |
@tgeng Thank you! |
Thanks for the quick response! When can I expect another release? (I can build our own, but we still want to make it clean by using the official build eventually 😉 ) |
I will upload it now! |
Hi friends at Tinder! First thank you for making this awesome project! I work for Pinterest and we are evaluating adopting this over our in-house solution.
One issue I am seeing is that bazel-diff seems to treat the entire external repo as one opaque blob. For example, if one uses this with
maven_install
, any single third party dependency change ends up trigger a global rebuild.This PR adds a flag that makes bazel-diff generate fine-grained hash for the explicitly mentioned external repos. This way, bazel-diff is smarter when handling external repos like
@maven
in a monorepo setting.Usage:
pass
--fineGrainedHashExternalRepos maven1,maven2
togenerate-hashes
command and fine-grained hashes are generated for targets in the listed external repos.Note: This is still a draft and hence I have not added any tests to this yet. I would like to get some input on this approach before that. I have tested this with a mono repo with >4M lines of Java code and it seems to be working as expected.