-
Notifications
You must be signed in to change notification settings - Fork 899
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: add cleanup disk step before publish #4394
Conversation
Signed-off-by: Philippe Scorsolini <p.scorsolini@gmail.com>
renovate will take care of pinning the hash in a dedicated PR once this one is merged. |
Related PRs for v1.11 and v1.12: |
android: true | ||
dotnet: true | ||
haskell: true |
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.
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.
"True" means "delete them" so it's a good thing these don't sound familiar to you, it means we are not deleting anything useful 😂
Successfully created backport PR for |
Would this also clean up the go package caches?
|
@@ -305,6 +305,16 @@ jobs: | |||
if: needs.detect-noop.outputs.noop != 'true' | |||
|
|||
steps: | |||
- name: Cleanup Disk | |||
uses: jlumbroso/free-disk-space@main |
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.
@phisco just a hint that, as discussed in crossplane-contrib/provider-aws#1888 (comment), this always defaults to what is in the main
and might better be pinned.
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.
Oh, I was expecting renovate to propose that change after merge 🤔 good catch!
Description of your changes
Recently we've had many cases of errors due to "no space left on device" during the publish step in the CI job, this is a pretty common issue with multi arch images' builds, so we decided to add a preliminary cleanup step at the beginning of the publish step to cleanup a few unneeded files (saving ~30GB).
With @ezgidemirel we had to merge it first on release-1.11 and release-1.12 branches because it was blocking the release of 1.13. But it's definitely worth adding it to master and backport it to 1.13 too, although we were lucky and didn't hit that on the latter.
I have:
Added or updated unit and E2E tests for my change.Runmake reviewable
to ensure this PR is ready for review.Addedbackport release-x.y
labels to auto-backport this PR if necessary.