-
Notifications
You must be signed in to change notification settings - Fork 54
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 images plugin #934
Conversation
ae14fc7
to
ef7505b
Compare
6baf762
to
cb1aab6
Compare
Rebased on top of #935 |
62f9517
to
555d5d6
Compare
Signed-off-by: Ettore Di Giacinto <edigiacinto@suse.com>
Signed-off-by: Ettore Di Giacinto <edigiacinto@suse.com>
Signed-off-by: Ettore Di Giacinto <edigiacinto@suse.com>
Signed-off-by: Ettore Di Giacinto <edigiacinto@suse.com>
This breaks validation as ver-1 is lower than ver See: #923 Signed-off-by: Ettore Di Giacinto <edigiacinto@suse.com>
555d5d6
to
3a61a70
Compare
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.
Yikes. Can't we simply docker system prune -a and call it a day? That should clean up everything not being used no?
Also, what do we expect to clean up from this? Aren't ci nodes spin up from scratch on each job?
Yes and no, I mean we definitely can delete all images after we finish building one package, the plugin is just a safeguard to avoid going to look at this again
Nope, we run 1 job building all images, rationale is explained #917 . we can split build into multiple, but that has other problems as well (starvation) |
I think with #278 we can disable the plugin and the cleanup, and just run it after the whole build.. but keeping it for now until we have self-hosted runners |
Attempt to free up space during build (related to #917 )