[CI] Add a scheduled workflow to clean up old versions#4
Conversation
|
Demo job (without actually pushing the changes), to show this worked as expected: https://github.com/CliMA/OceananigansDocumentation/actions/runs/20192351427/job/57971528829?pr=4 |
It's already available in most (but not all) GitHub Actions images, but better to be safe.
c733ee6 to
a6c3eaa
Compare
This reverts commit a6c3eaa.
|
|
||
| # Simple sanity check: make sure we didn't find too many versions to delete, that'd be | ||
| # suspicious, and a hint that something went wrong | ||
| old_versions_threshold = 5 |
There was a problem hiding this comment.
eg, we can find multiple versions to clean up when there are a few bumps within the cron window?
There was a problem hiding this comment.
which is once a week if I read that correctly
There was a problem hiding this comment.
Yes. This is a simple stupid check in case the script does something silly and unexpected and tries to delete too much stuff.
|
But we will still be able to find old versions ? Or is the idea that we will only host minor versions and not patches. |
|
This script automates what @navidcy has been doing manually: remove all old patch versions, and keep only the latest one for each minor version. |
No description provided.