ci: use BUILD_TAG in functional tests image identifier #7076
+9
−4
Conversation
This file contains hidden or 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
Member
Jenkins BuildsClick to see older builds (6)
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #7076 +/- ##
============================================
+ Coverage 34.94% 59.96% +25.01%
============================================
Files 798 813 +15
Lines 111352 113425 +2073
============================================
+ Hits 38915 68015 +29100
+ Misses 67539 38555 -28984
- Partials 4898 6855 +1957
Flags with carried forward coverage won't be shown. Click here to find out more. |
igor-sirotin
force-pushed
the
ci/functional-tests-use-BUILD_TAG
branch
from
7334dd1 to
fffda0d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Use
BUILD_TAGinstead ofBUILD_ID, because the latter is is just the build number, like3.This was leading to conflicts between different PRs.