feat: Tag docker image with major.minor version #20
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
fmarek-kindred
force-pushed
the
feature/produce_additional_docker_tag
branch
from
06ef74c to
35dd380
Compare
gk-kindred
approved these changes
Mar 18, 2024
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 changes github action pipeline by:
Creating additional a) docker tag; b) git tag.
To make it easier to refer to the specific "latest stable" PIT version, we add additional generic tag made of 1st two segments of original tag.
A) When we build docker image tagged as v2.0.10 then we will also automagically tag that image with "v2.0", where the new tag will be made from original user tag.
B) We will also tag repo with new tag "v2.0". If it already exists then the new tag will be moved to the new commit.