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

CI: opt-in gradle-home-cache-cleanup: true #339

Merged
merged 2 commits into from
Mar 18, 2023
Merged

CI: opt-in gradle-home-cache-cleanup: true #339

merged 2 commits into from
Mar 18, 2023

Conversation

martinbonnin
Copy link
Collaborator

I'm not 100% clear where the good place to put this is. Looks like the gradle-build-action config and cache key is global to the workflow so putting it in the initial setup is the correct place but maybe it needs to be in the last one, not 100% sure.

See also gradle/actions#26

@@ -22,6 +22,8 @@ jobs:

- name: Setup Gradle
uses: gradle/gradle-build-action@v2
with:
gradle-home-cache-cleanup: true
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is the only one that actually runs on main.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense. That also means if a PR workflow uses a big dependency, the next MAIN workflow will most likely delete it because it wasn't used during the run. I think that's acceptable as MAIN should do most of the work. Anyways, I'll remove the other ones.

@joreilly joreilly merged commit 4a93844 into main Mar 18, 2023
@joreilly joreilly deleted the gradle-cleanup branch March 18, 2023 14:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants