ci/release: create tagged container images #4125
Merged
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
rst0git
force-pushed
the
ci-release-ctr-img
branch
from
5d83dd2
to
0be1e80
Compare
This patch updates the release GitHub action to build & push a container image in DockerHub when a new p4c release is created. Suggested-by: Fabian Ruffy <[email protected]> Signed-off-by: Radostin Stoyanov <[email protected]>
rst0git
force-pushed
the
ci-release-ctr-img
branch
from
0be1e80
to
71b8aff
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.
This pull request updates the release GitHub action to build & push a container image in DockerHub when a new p4c release is created.
Example: https://hub.docker.com/r/rstoyanov/p4c/tags
Fixes: #4123