You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Sometimes we want to restrict the disk usage of a repository. Therefore it would be nice if we somehow can define a quota on repository size.
Describe the solution you'd like
Option to define a quota on a repository based on disksize and/or amount of packages
Describe alternatives you've considered
none
Additional context
We use build pipelines a lot that deploy their nightly builds. In time this can grow so large it fills the disk. To prevent this we would like to quota these kind of repositories
The text was updated successfully, but these errors were encountered:
What would be the behavior of the quota that you are looking for? Stop the packages from being added, remove old packages, combination of both?
While not what you asked for, currently you could set up a cron job to run the reclaim task on your nightly repositories if the content is no longer needed.
The default behavior of the quota would be blocking the upload.
I would not classify removal of packages a functionality of a quota. That would most likely fall under another clean up task where we can specify the criteria for removal, like older then x days or keep last 10 versions .
Is your feature request related to a problem? Please describe.
Sometimes we want to restrict the disk usage of a repository. Therefore it would be nice if we somehow can define a quota on repository size.
Describe the solution you'd like
Option to define a quota on a repository based on disksize and/or amount of packages
Describe alternatives you've considered
none
Additional context
We use build pipelines a lot that deploy their nightly builds. In time this can grow so large it fills the disk. To prevent this we would like to quota these kind of repositories
The text was updated successfully, but these errors were encountered: