Replies: 1 comment
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
We currently publish container images from a few PUBLIC github repositories to quay.io & docker.io . This is for a) Releases (also tagged latest) and b) snapshots. We do not publish from PRs
To help developers do additional verification on their changes, I'm wondering about publishing from PRs, but also wary about creating too much 'noise' on our existing repos.
Github packages appears to offer a container registry, so I wonder if we could publish from a PR to there. Even better to do so with limited expiry - say causing all PR images to expire after 2 weeks or a month. I don't see that packages has this feature, so I wonder if we'd blow the any size limits quickly?
Another issue is likely permissions - we use a fork and pull model, so the PR will have more limited permissions - no access to secrets for example (another reason we couldn't so easily publish to quay/docker) - is this easier with github packages (which I've not used before)
Beta Was this translation helpful? Give feedback.
All reactions