Skip to content

Explicitly disable maven repo caching for selected jobs #18044

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

Merged
merged 2 commits into from
Jun 27, 2023

Conversation

losipiuk
Copy link
Member

@losipiuk losipiuk commented Jun 26, 2023

Release notes

(x) This is not user-visible or docs only and no release notes are required.
( ) Release notes are required, please propose a release note for me.
( ) Release notes are required, with the following suggested text:

@cla-bot cla-bot bot added the cla-signed label Jun 26, 2023
@losipiuk losipiuk force-pushed the lo/cache-imp branch 4 times, most recently from 68a558c to 04420f2 Compare June 26, 2023 16:00
losipiuk added 2 commits June 26, 2023 18:01
Useful for jobs which can make use of cached maven repo
but are not downloading whole repo by themselves so the maven repo
as left by the job should not be cached.
Previously .m2/repository caching was disabled for some jobs which
do not ensure complete maven repository at the end of execution
by deleting .m2/repository directory.

This commit changes mechanism for that to explicitly mark requeste
behaviour via `cache: restore` parameter passed to` setup action.
@losipiuk losipiuk requested a review from nineinchnick June 27, 2023 08:37
@losipiuk losipiuk merged commit a1b917f into trinodb:master Jun 27, 2023
@github-actions github-actions bot added this to the 421 milestone Jun 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants