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

Add cleanup functionality for the canary-release workflow #30

Open
jezdez opened this issue Mar 1, 2022 · 4 comments
Open

Add cleanup functionality for the canary-release workflow #30

jezdez opened this issue Mar 1, 2022 · 4 comments
Labels
backlog issue has been triaged but has not been earmarked for any upcoming release good first issue great for new contributors, code change is envisioned to be trivial/relatively straight-forward source::anaconda created by members of Anaconda, Inc. stale::recovered [bot] recovered after being marked as stale type::feature request for a new feature or capability

Comments

@jezdez
Copy link
Member

jezdez commented Mar 1, 2022

We should add an option cleanup feature to the canary-release workflow that allows deleting the channel's N packages (or by time) automatically when running the workflow. That way we reduce the risk of overflowing the hard disk limits of anaconda.org account (10G).
@kenodegard kenodegard added source::anaconda created by members of Anaconda, Inc. type::feature request for a new feature or capability labels Mar 3, 2022
@kenodegard
Copy link
Contributor

Is there an API call for this?

cc: @chenghlee

@chenghlee
Copy link

Yeah; maybe DELETE /release/{owner}/{package}/{version}? See https://api.anaconda.org/docs.

@kenodegard kenodegard added the backlog issue has been triaged but has not been earmarked for any upcoming release label Mar 24, 2022
@beeankha beeankha added the good first issue great for new contributors, code change is envisioned to be trivial/relatively straight-forward label Mar 31, 2022
@github-actions
Copy link

github-actions bot commented Apr 1, 2023

Hi there, thank you for your contribution!

This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs.

If you would like this issue to remain open please:

  1. Verify that you can still reproduce the issue at hand
  2. Comment that the issue is still reproducible and include:
    - What OS and version you reproduced the issue on
    - What steps you followed to reproduce the issue

NOTE: If this issue was closed prematurely, please leave a comment.

Thanks!

@github-actions github-actions bot added the stale [bot] marked as stale due to inactivity label Apr 1, 2023
@kalawac
Copy link

kalawac commented Apr 19, 2023

Do we still want this? It's about to be closed as stale.

@github-actions github-actions bot added stale::recovered [bot] recovered after being marked as stale and removed stale [bot] marked as stale due to inactivity labels Apr 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
backlog issue has been triaged but has not been earmarked for any upcoming release good first issue great for new contributors, code change is envisioned to be trivial/relatively straight-forward source::anaconda created by members of Anaconda, Inc. stale::recovered [bot] recovered after being marked as stale type::feature request for a new feature or capability
Projects
🧭 Planning
Status: No status
Milestone
No milestone
Development

No branches or pull requests
5 participants
@jezdez @chenghlee @kenodegard @kalawac @beeankha