-
Notifications
You must be signed in to change notification settings - Fork 25.6k
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
build(bazel): improve remote caching for AIO local deps build #48579
Conversation
5c1bbcb
to
7645553
Compare
7645553
to
dd13eb3
Compare
dd13eb3
to
f410824
Compare
@@ -125,7 +125,6 @@ copy_to_directory( | |||
# All source and configuration files required to build the docs app | |||
APPLICATION_FILES = [ | |||
"angular.json", | |||
"package.json", |
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.
This wasn't a necessary input to the architect actions.
2f9f5ae
to
be28415
Compare
Fix non-hermetic zipping of example zips by fixing the zip entry timestamps. I also hardcoded stamp values in stable-status.txt and volatile-status.txt using the workspace status command for the aio_local_deps config to improve cache performance. The Bazel remote cache appears to not ignore volatile-status.txt when there are no other changes, unlike the local Bazel cache: bazelbuild/bazel#10075 (comment)
be28415
to
62e7ceb
Compare
Note that the architect build ( |
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.
Nice, thanks!
// and will invalidate actions that depend on it when the values change. | ||
// https://github.com/bazelbuild/bazel/issues/10075#issuecomment-546872111 | ||
console.log(`\ | ||
BUILD_TIMESTAMP 0 |
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.
One thing I found interesting from the Bazel issue. It sounds like we shouldn't really rely on stamping for development builds. This makes a lot of sense to me. I think this is a great improvement regardless and solves the issue, but I wonder if long-term Angular should make sure AIO can be built w/ local packages unstamped? I believe we could patch/configure architect appropriately
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.
I agree that altering architect is probably the right long-term solution.
This PR was merged into the repository by commit 0ae80a7. |
Fix non-hermetic zipping of example zips by fixing the zip entry timestamps. I also hardcoded stamp values in stable-status.txt and volatile-status.txt using the workspace status command for the aio_local_deps config to improve cache performance. The Bazel remote cache appears to not ignore volatile-status.txt when there are no other changes, unlike the local Bazel cache: bazelbuild/bazel#10075 (comment) PR Close #48579
…r#48579) Fix non-hermetic zipping of example zips by fixing the zip entry timestamps. I also hardcoded stamp values in stable-status.txt and volatile-status.txt using the workspace status command for the aio_local_deps config to improve cache performance. The Bazel remote cache appears to not ignore volatile-status.txt when there are no other changes, unlike the local Bazel cache: bazelbuild/bazel#10075 (comment) PR Close angular#48579
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Architect tests for the AIO local deps build run on every pull request.
What is the new behavior?
Test results are cached properly, significantly speeding up the build when there are no AIO changes.
Does this PR introduce a breaking change?