Fix conflicted containers in Jenkins tests - #561
Open
oksana-grishchenko wants to merge 3 commits into
Open
Conversation
oksana-grishchenko
requested review from
egegunes,
jvpasinatto,
mayankshah1607,
nmarukovich and
valmiranogueira
July 30, 2026 09:39
Contributor
|
egegunes
approved these changes
Jul 31, 2026
Contributor
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Problem:
when re-running Jenkins pipeline, a conflict appears in Docker:
see the run
It blocks the CI, re-run helps only eventually when the other container is gone.
The problem is that we use hardcoded container name which could conflict with a running/orphaned container.
Suggestion:
Do not hardcode the container name and clean up orphaned containers before each run.