Skip to content

Comments

Replace manual disk cleanup with quick-cleanup#360

Closed
sebrandon1 wants to merge 1 commit intoopenshift:mainfrom
sebrandon1:use-quick-cleanup
Closed

Replace manual disk cleanup with quick-cleanup#360
sebrandon1 wants to merge 1 commit intoopenshift:mainfrom
sebrandon1:use-quick-cleanup

Conversation

@sebrandon1
Copy link
Member

@sebrandon1 sebrandon1 commented Feb 18, 2026

Summary

Replace manual disk cleanup scripts with the shared palmsoftware/quick-cleanup GitHub Action.

This consolidates the "Reclaim disk space" steps (docker image prune + rm -rf dotnet, android) into a single maintained action across 2 workflows. It also provides automatic Docker storage relocation to the larger /mnt partition.

Already in use

quick-cleanup is already adopted in production workflows across multiple repos:

Related PRs

Tracking

Changes

  • Updated .github/workflows/publish.yaml — replaced "Reclaim disk space" block
  • Updated .github/workflows/test-prom-version-upgrade.yaml — replaced "Reclaim disk space" block

Benefits

  • Less boilerplate — replaces manual cleanup across 2 workflows
  • Docker relocation — automatically moves Docker storage to /mnt (larger partition)
  • Adaptive cleanup — adjusts intensity based on available space
  • Disk reporting — built-in before/after df -h output
  • Maintained upstream — cleanup targets updated as runner images change
  • Apache 2.0 licensed

Consolidates manual disk cleanup into a shared, maintained action that
also provides automatic Docker storage relocation to /mnt.
@openshift-ci openshift-ci bot requested review from jan--f and slashpai February 18, 2026 15:51
@openshift-ci
Copy link

openshift-ci bot commented Feb 18, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sebrandon1
Once this PR has been reviewed and has the lgtm label, please assign simonpasquier for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jan--f
Copy link

jan--f commented Feb 18, 2026

The openshift org does not use actions.
Is this a coordinated effort? Any jira issue attached to this?

/hold
Unless something is going to change with regards to actions in the openshift org I'm 👎 on this as we don't want downstream commits to maintain.

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 18, 2026
@sebrandon1
Copy link
Member Author

Ah I was just doing a broad search for repos that had this sort of cleanup happening in their .github folders since I noticed it elsewhere. No need for this if you don't actually have Actions enabled 👍

Thanks @jan--f I can mark this one as closed.

@sebrandon1
Copy link
Member Author

Closing — GitHub Actions is not enabled on this fork (only Dependabot dependency graph updates run here). The upstream workflows are not executed in this repo.

@sebrandon1 sebrandon1 closed this Feb 18, 2026
@openshift-ci
Copy link

openshift-ci bot commented Feb 18, 2026

@sebrandon1: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/security 3707082 link false /test security

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

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

Labels

do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants