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.
On every commit to main (except for some ignored files) the Preview - CI action will, among others, publish NuGet packages to the preview feed.
We store the preview package feed on Cloudsmith. For this, Cloudsmith provides free hosting.
Previously, we could store GBs of packages (maybe up to 100 GB?) for 180 days. Cloudsmith will restrict this to 10k packages soon and we need to figure out how to adapt to this.
Describe the solution you'd like
Instead of a publish on every push, we could have a single publish every day if there were new commits (i.e. a "nightly"). This is only for the package publish; we'd still have a CI build for every commit as of today.
Ideally, we could say to our users that the preview packages are guaranteed to be available for x days (while still recommending not to use them in production). While we won't be able to say exactly that, we could approximate: We publish 186 packages currently, so that's ~53 days of packages if we publish every day.
Describe alternatives you've considered
We could clean up the oldest packages without downloads too. The Cloudsmith CLI can be used to fetch this data (I guess its metrics packages command) and to delete packages (delete). However, this looks a bit too complex for this use case.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
On every commit to
main
(except for some ignored files) the Preview - CI action will, among others, publish NuGet packages to the preview feed.We store the preview package feed on Cloudsmith. For this, Cloudsmith provides free hosting.
Previously, we could store GBs of packages (maybe up to 100 GB?) for 180 days. Cloudsmith will restrict this to 10k packages soon and we need to figure out how to adapt to this.
Describe the solution you'd like
Instead of a publish on every push, we could have a single publish every day if there were new commits (i.e. a "nightly"). This is only for the package publish; we'd still have a CI build for every commit as of today.
Ideally, we could say to our users that the preview packages are guaranteed to be available for x days (while still recommending not to use them in production). While we won't be able to say exactly that, we could approximate: We publish 186 packages currently, so that's ~53 days of packages if we publish every day.
Describe alternatives you've considered
We could clean up the oldest packages without downloads too. The Cloudsmith CLI can be used to fetch this data (I guess its
metrics packages
command) and to delete packages (delete
). However, this looks a bit too complex for this use case.The text was updated successfully, but these errors were encountered: