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.

Sign up for GitHub

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

Jump to bottom

Strategy for pruning old builds #25

Open
agis opened this issue Apr 12, 2018 · 1 comment
Open

Strategy for pruning old builds #25

agis opened this issue Apr 12, 2018 · 1 comment
Labels
feature server
Milestone
1.0

Comments

@agis
Copy link
Contributor

agis commented Apr 12, 2018 •
edited

There should be a strategy for somehow pruning old builds. This could be in the form of a "retention period" configuration.

This is necessary, otherwise disk usage will grow indefinitely.
@agis agis added this to the 1.0 milestone Apr 12, 2018
@agis agis added the server label Apr 12, 2018
@agis agis added the feature label Apr 24, 2018
@agis agis mentioned this issue Apr 24, 2018
Merged
apostergiou added a commit that referenced this issue Apr 25, 2018
@apostergiou
Add purger script for removing stale jobs
8970581 
A best-effort, temporary solution to #25.

The script will be replaced later when we implement a solution built-in
to mistryd.
apostergiou added a commit that referenced this issue Apr 25, 2018
@apostergiou
Add purger script for removing stale jobs
ca903e5 
A best-effort, temporary solution to #25.

The script will be replaced later when we implement a solution built-in
to mistryd.
apostergiou added a commit that referenced this issue Apr 25, 2018
@apostergiou
Add purger script for removing stale jobs (#55)
b528fa0 
A best-effort, temporary solution to #25.

The script will be replaced later when we implement a solution built-in
to mistryd.
@agis
Copy link
Contributor Author

agis commented Jul 27, 2018

We now have a script for doing this. Ideally, we want the server to do this automatically. One should be able to configure how much usage each project should consume and how much total usage all projects should consume.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature server
Projects
None yet
Milestone
1.0
Development

No branches or pull requests
1 participant
@agis