-
Notifications
You must be signed in to change notification settings - Fork 6.1k
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
Avoid redundant bazel build #4458
Conversation
@@ -1,2 +1,4 @@ | |||
# build config | |||
build --compilation_mode=opt | |||
build --action_env=PATH |
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.
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.
It is still needed, otherwise we can't guarantee which python will be picked up if there are multiple ones.
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.
ok, just noticed that the build.sh
script takes a -p
option.
Java CI time reduced from 32min to 17min |
Can one of the admins verify this patch? |
Test FAILed. |
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.
LGTM, but let's be careful to monitor that introducing PATH into the python build doesn't break things (i.e. different binaries might be picked up based on whether PATH is set or not).
What do these changes do?
Bazel will invalidate caches if the command-line options are different. This PR puts all needed
action_env
s in the.bazelrc
file to avoid cache invalidation.Related issue number