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: add cleanup disk step before publish #4394

Merged
merged 1 commit into from
Jul 27, 2023

Conversation

phisco
Copy link
Contributor

@phisco phisco commented Jul 27, 2023

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:

  • Read and followed Crossplane's contribution process.
  • Added or updated unit and E2E tests for my change.
  • Run make reviewable to ensure this PR is ready for review.
  • Added backport release-x.y labels to auto-backport this PR if necessary.

Signed-off-by: Philippe Scorsolini <p.scorsolini@gmail.com>
@phisco phisco requested a review from ezgidemirel July 27, 2023 14:25
@phisco phisco requested review from a team as code owners July 27, 2023 14:25
@phisco phisco requested a review from bobh66 July 27, 2023 14:25
@phisco
Copy link
Contributor Author

phisco commented Jul 27, 2023

renovate will take care of pinning the hash in a dedicated PR once this one is merged.

@jbw976
Copy link
Member

jbw976 commented Jul 27, 2023

Related PRs for v1.11 and v1.12:

Comment on lines +311 to +313
android: true
dotnet: true
haskell: true
Copy link
Member

Choose a reason for hiding this comment

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

the names of these values don't look applicable to our project, and the readme just says

Most of the options are self-explanatory.

wondering if these are actually needed, but i do see its the same values we already put into #4391 and #4392, so i'm not inclined to rock the boat now 😂

Copy link
Contributor Author

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 😂

@phisco phisco merged commit bf7c63d into crossplane:master Jul 27, 2023
15 checks passed
@github-actions
Copy link

Successfully created backport PR for release-1.13:

@turkenh
Copy link
Member

turkenh commented Jul 28, 2023

Would this also clean up the go package caches?

https://github.com/phisco/crossplane/blob/a89cf4dc89cae98f1d959bfca5d6d68f5db6fa3d/.github/workflows/ci.yml#L342

  - name: Find the Go Build Cache
    id: go
    run: echo "cache=$(make go.cachedir)" >> $GITHUB_OUTPUT

@@ -305,6 +305,16 @@ jobs:
if: needs.detect-noop.outputs.noop != 'true'

steps:
- name: Cleanup Disk
uses: jlumbroso/free-disk-space@main
Copy link
Contributor

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.

Copy link
Contributor Author

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants