-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cleanup before workspace start #16498
cleanup before workspace start #16498
Conversation
Signed-off-by: Michal Vala <mvala@redhat.com>
Signed-off-by: Michal Vala <mvala@redhat.com>
@@ -410,6 +410,7 @@ public void startsKubernetesEnvironment() throws Exception { | |||
verify(services).create(any()); | |||
verify(secrets).create(any()); | |||
verify(configMaps).create(any()); | |||
verify(namespace).cleanUp(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know, currently, the test does not respect the order but still, it would be better to put this call where it's expected to be called, somewhere before verify(deployments).deploy(any(Pod.class))
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've added an extra test for this case, to not increase complexity of this one...
Signed-off-by: Michal Vala <mvala@redhat.com>
✅ E2E Happy path tests succeed 🎉 See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1) |
This reverts commit 983d0a5. Signed-off-by: Sergii Kabashniuk <skabashniuk@redhat.com>
Signed-off-by: Michal Vala mvala@redhat.com
What does this PR do?
Cleanup workspace objects before start to avoid failures when creating.
What issues does this PR fix or reference?
#16418
Release Notes
Docs PR