-
Notifications
You must be signed in to change notification settings - Fork 83
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
github: push charon to official docker hub registry #782
Conversation
Codecov Report
@@ Coverage Diff @@
## main #782 +/- ##
==========================================
+ Coverage 54.11% 54.50% +0.39%
==========================================
Files 109 109
Lines 10667 10667
==========================================
+ Hits 5772 5814 +42
+ Misses 4033 3991 -42
Partials 862 862
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this build once for each target repository? It would be great if the binaries are built once and then pushed to the different targets...
- uses: docker/build-push-action@v2 | ||
with: | ||
context: . | ||
platforms: linux/amd64,linux/arm64 | ||
push: true | ||
build-args: GITHUB_SHA=${{ github.sha }} | ||
tags: ${{ steps.meta.outputs.tags }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems like multiple registries are supported by docker/build-push-action
, so can remove this section and just move dockerhub login up next to ghcr login.
Pushes the charon image to docker hub after ghcr. Needs to be tested by being merged. Potentially we don't want to send dev builds here too and might want to split this to only run on tags not commits to main.
category: misc
ticket: #781