Change docker image naming convention for BFS7.7.1 #59
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
2samueld
changed the title
sichend
reviewed
Nov 18, 2021
sichend
approved these changes
Nov 18, 2021
Tengda-He
approved these changes
Nov 18, 2021
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.
Description:
This PR fixes the naming convention of the docker image. In jenkins job number 17 for bfs7.7.1 and bfs 6.5.4, two separate jobs but with the same name "test-image:17" were concurrently ran. This caused failure in the node environment because the jenkins job for bfs7.7.1 and bfs6.5.4 was pointing to the same docker container "test-image:17"
bfs7.7.1 job 17: https://jenkins.bfs.sichend.people.aws.dev/job/Kibana/job/bfs7.7.1/17/
bfs6.5.4 job 17: https://jenkins.bfs.sichend.people.aws.dev/job/Kibana/job/bfs6.5.4/17/
Close the node environment issue in #57