-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Improve GitHub Actions cache usage #43568
Conversation
f66f50a
to
7728520
Compare
This comment has been minimized.
This comment has been minimized.
7728520
to
d8675ba
Compare
This comment has been minimized.
This comment has been minimized.
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, a few suggestions below.
We use the ones coming from the push events. Related to quarkusio#43559
This can be useful when pushing small iterations to a pull request. It is limited to pull requests only and only for the Initial JDK build. We will check if it improves things and the size of the cache. Related to quarkusio#43559
d8675ba
to
6af48cc
Compare
This comment has been minimized.
This comment has been minimized.
6af48cc
to
e7c2f56
Compare
Status for workflow
|
This is related to #43559.
The idea is to avoid saving the .m2 cache for pull requests and to only restore the cache coming from the push events.
Also we want to experiment with caching the Develocity local cache but this might be a bit cumbersome given the number of jobs we have: experimenting with the Initial JDK build first.