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

better story on which container registry we use? #2318

Open
beckermr opened this issue Sep 27, 2024 · 1 comment
Open

better story on which container registry we use? #2318

beckermr opened this issue Sep 27, 2024 · 1 comment

Comments

@beckermr
Copy link
Member

Right now we upload some of our images to quay and docker, others to docker only. Further, we don't make use of github's packages (due to permissions issues IIRC).

It'd be nice to fix this up so we

  • push all images everywhere?
  • make use of github if we can
  • have our CI + feedstock jobs use only one source?

Thoughts?

@jaimergp
Copy link
Member

jaimergp commented Oct 2, 2024

Consistency would help, yes :) If we are going to push everywhere, it would be nice if the backend was configurable through a quick setting somewhere too. For example, in feedstocks folks could rerender via conda-forge.yml edits if Quay.io is down, and in our infra we could leverage Action variables at the org or repo level to control that.

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

No branches or pull requests

2 participants