[TT-1600] corrected handling of tags #14312
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
… if compatibility pipeline is triggered by tag
Tofel
force-pushed
the
tt_1600_tag_in_compat_pipeline
branch
from
0bbc572 to
2d37920
Compare
|
there is a |
Tofel
force-pushed
the
tt_1600_tag_in_compat_pipeline
branch
from
2d37920 to
7867c48
Compare
momentmaker
approved these changes
Sep 4, 2024
lukaszcl
approved these changes
Sep 4, 2024
kalverra
approved these changes
Sep 4, 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.
Background:
Tags were incorrectly handled, because they do not map
1:1to Docker images. From the latter ones we stripvprefix, so thatv2.15.0becomes2.15.0. This wasn't handled properly as I assumed that both are identical.Additionally, Slack handle that should be informed was changed to one that disturbs less people.
Tests:
v2.14.0for the first time -> image is build, test is run executionv2.14.0for the second time -> image building is skipped, test is run execution