-
Notifications
You must be signed in to change notification settings - Fork 7
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
Publish images to GitHub Container Registry #29
Comments
Using GitHub's container registry is great. It would be good to document the change from an end-user perspective. If I used to |
agree
the org changes from non hyphenated to hyphenated pact-foundation a user may need to login to ghcr registry with their docker client |
- create linux executables linked statically to musl - drop gnu (glibc) target, executable will work on alpine & glibc based distros (debian etc) - create windows aarch64 target - required update to Cargo.lock to update ring to v0.17 due to build failures on v0.16 - refactor release script & workflow to match pact-reference - builds on pull request to master/main branch, in debug mode - add Docker automated pipeline during release - publish multi-arch amd64/arm64 - publish to DockerHub - publish to GitHub container registry Related epics - musl all the things - pact-foundation/roadmap#30 - publish to github container registry - pact-foundation/roadmap#29
- create linux executables linked statically to musl - drop gnu (glibc) target, executable will work on alpine & glibc based distros (debian etc) - create windows aarch64 target - required update to Cargo.lock to update ring to v0.17 due to build failures on v0.16 - refactor release script & workflow to match pact-reference - builds on pull request to master/main branch, in debug mode - add Docker automated pipeline during release - publish multi-arch amd64/arm64 - publish to DockerHub - publish to GitHub container registry Related epics - musl all the things - pact-foundation/roadmap#30 - publish to github container registry - pact-foundation/roadmap#29
Pact Stub ServerNow complete DockerHub
Github Container Registry
|
Can this also be implemented for the pact-ref-verifier image from the pact-reference repository? I noticed that recent versions from that repo haven't been pushed to any registry (see pact-foundation/pact-reference#446). |
yep sorry haven't got round to adding an auto publish to docker for the verifier and mock server cli. will look to get in place possibly next week |
In order to avoid users who may be affected by rate limiting pulling images from DockerHub, it would be prudent to provide images published to GHCR
Dockerhub profile :- https://hub.docker.com/u/pactfoundation
Images / Repos and Build locations
Delta of required changes
https://github.com/pact-foundation/pact-ruby-cli/pull/127/files
Progress
The text was updated successfully, but these errors were encountered: