Build & publish docker image as part of release CI #376
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kacperzuk-neti
force-pushed
the
build-docker-image-during-release
branch
3 times, most recently
from
4a9373a to
39d0ae7
Compare
kacperzuk-neti
force-pushed
the
build-docker-image-during-release
branch
from
39d0ae7 to
92f052a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I consistently forget to push new docker image to Docker Hub manually. Doesn't matter for runtime-only upgrades, but will matter when we need to change chain-spec or node. With this change, image will be built automatically during release and published on GitHub Container Registry.