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

ci: clean old container images, document how to push images #1530

Open
1 of 2 tasks
avivace opened this issue Oct 2, 2024 · 2 comments
Open
1 of 2 tasks

ci: clean old container images, document how to push images #1530

avivace opened this issue Oct 2, 2024 · 2 comments
Assignees
Labels
builds This affects the build process or release artifacts
Milestone

Comments

@avivace
Copy link
Member

avivace commented Oct 2, 2024

Following up #1509 :

  • document how to manually push an image (e.g. old tag, without having to repush it)
  • find a way to clean up the old artifacts
@Rangi42 Rangi42 added this to the v0.9.0 milestone Oct 2, 2024
@Rangi42 Rangi42 added the builds This affects the build process or release artifacts label Oct 2, 2024
@Rangi42
Copy link
Contributor

Rangi42 commented Nov 28, 2024

@avivace Any updates on auto-deleting all those sha256:... packages?

@ISSOtm
Copy link
Member

ISSOtm commented Nov 28, 2024

GITHUB_TOKEN cannot be granted admin permissions for a scope (only read, write, or none), and admin perms are required to delete containers.

So I think what needs to be done, is for @avivace to generate a PAT for the gbdev org (so it's not tied to a specific maintainer), and pass that to the action via secrets.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
builds This affects the build process or release artifacts
Projects
None yet
Development

No branches or pull requests

3 participants