Skip to content
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

Merged
merged 4 commits into from
Oct 1, 2024
Merged

Conversation

gsmet
Copy link
Member

@gsmet gsmet commented Sep 27, 2024

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.

@quarkus-bot quarkus-bot bot added the area/infra-automation anything related to CI, bots, etc. that are used to automated our infrastructure label Sep 27, 2024

This comment has been minimized.

@gsmet gsmet force-pushed the improve-cache-usage branch 2 times, most recently from 7728520 to d8675ba Compare September 28, 2024 15:45

This comment has been minimized.

Copy link
Member

@yrodiere yrodiere left a 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.

.github/workflows/ci-actions-incremental.yml Show resolved Hide resolved
.github/workflows/ci-actions-incremental.yml Outdated Show resolved Hide resolved
@gsmet gsmet requested a review from yrodiere September 30, 2024 08:12
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

This comment has been minimized.

Copy link

quarkus-bot bot commented Sep 30, 2024

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit e7c2f56.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

@gsmet gsmet merged commit 2490380 into quarkusio:main Oct 1, 2024
52 checks passed
@quarkus-bot quarkus-bot bot added this to the 3.16 - main milestone Oct 1, 2024
@gsmet gsmet modified the milestones: 3.16.0.CR1, 3.15.2 Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/infra-automation anything related to CI, bots, etc. that are used to automated our infrastructure
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants