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

Clean up the horti staging database #5129

Closed
garethbowen opened this issue Dec 20, 2018 · 3 comments
Closed

Clean up the horti staging database #5129

garethbowen opened this issue Dec 20, 2018 · 3 comments
Assignees
Labels
Priority: 2 - Medium Normal priority Type: Technical issue Improve something that users won't notice
Projects

Comments

@garethbowen
Copy link
Member

garethbowen commented Dec 20, 2018

The horti staging db ( https://staging.dev.medicmobile.org ) stores all our published artefacts so they can later be installed. Currently all tags (released versions) and branches (features in development) get published there and stored indefinitely. Once a branch gets merged/released there's no need to keep the build artefact around any more. Currently it's using 35GB which costs money and clogs up the horti UI with old branches.

Find a way to purge (or delete if purging isn't available) old feature branches. The simplest way is simply to delete them 3 months after the latest release. Be very careful not to delete tag releases.

If purging works then also update the scripts/travis/cleanup.js to purge instead of deleting the testing releases.

@SCdF
Copy link
Contributor

SCdF commented Dec 21, 2018

Be very careful not to delete tag releases.

FWIW the build server already blocks this for releases and betas via validate_doc_update. I have no idea if that function runs for purges though, I imagine not?

@garethbowen garethbowen added the Type: Technical issue Improve something that users won't notice label Apr 14, 2019
@garethbowen garethbowen added this to To do in 3.8.0 via automation Apr 14, 2019
@garethbowen garethbowen added the Priority: 2 - Medium Normal priority label Apr 14, 2019
@garethbowen
Copy link
Member Author

Prioritising so as to save some money on hosting fees. It should be simple enough to do...

@garethbowen garethbowen self-assigned this Dec 2, 2019
@garethbowen garethbowen moved this from To do to In progress in 3.8.0 Dec 2, 2019
garethbowen added a commit that referenced this issue Dec 2, 2019
garethbowen added a commit to medic/medic-builds-repo that referenced this issue Dec 2, 2019
garethbowen added a commit to medic/medic-builds-repo that referenced this issue Dec 3, 2019
garethbowen added a commit that referenced this issue Dec 4, 2019
@garethbowen
Copy link
Member Author

Merged. No AT required.

3.8.0 automation moved this from In progress to Done Dec 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: 2 - Medium Normal priority Type: Technical issue Improve something that users won't notice
Projects
No open projects
3.8.0
  
Done
Development

No branches or pull requests

2 participants