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

Daily preview package publish instead of on every commit to main #15548

Closed
Piedone opened this issue Mar 19, 2024 · 1 comment · Fixed by #15552
Closed

Daily preview package publish instead of on every commit to main #15548

Piedone opened this issue Mar 19, 2024 · 1 comment · Fixed by #15552
Assignees
Milestone

Comments

@Piedone
Copy link
Member

Piedone commented Mar 19, 2024

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.

@hishamco
Copy link
Member

Totally agree, this will reduce the number of packages deployed in CloudSmith

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants