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

Workflow for cleaning up runner #198

Merged
merged 7 commits into from
Aug 30, 2024
Merged

Workflow for cleaning up runner #198

merged 7 commits into from
Aug 30, 2024

Conversation

vmilosevic
Copy link
Collaborator

This workflow frees space on a runner by deleting the work folder and purging the docker cache.
Run workflow manually, choose cleanup options, and label the runner that is out of space.

Closes #196

Copy link
Contributor

@nvukobratTT nvukobratTT left a comment

Choose a reason for hiding this comment

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

Can we think about a more automatic way of doing this? E.g. is it possible to check the disk usage during initialization time, and do a cleanup like this?

@vmilosevic
Copy link
Collaborator Author

I'm afraid automating this will just hide problems and remove cached images and files too often. Let's have this workflow as emergency mitigation.

We should look into

  • requesting more storage for our VMs
  • reducing Docker image size

@nvukobratTT
Copy link
Contributor

@vmilosevic similar question, let's track these as new issues, just not to lose track of it. Is it possible for you to create them in FFE repo?

@vmilosevic vmilosevic merged commit 831b1b5 into main Aug 30, 2024
3 checks passed
@vmilosevic vmilosevic deleted the vmilosevic/cleanup branch September 3, 2024 09:25
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.

[CI] Hitting CI storage limits on push runs
2 participants