Skip to content
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

Use newer che-plugin-broker with che-theia remote runtime injection #14832

Merged

Conversation

AndrienkoAleksandr
Copy link
Contributor

What does this PR do?

Use newer che-plugin-broker with che-theia remote runtime injection. P.S. runtime injection begin work when we will merge init container for che-theia editor eclipse-che/che-plugin-registry#233, otherwise che-theia works in an old way.

What issues does this PR fix or reference?

#13387

Signed-off-by: Oleksandr Andriienko oandriie@redhat.com

Signed-off-by: Oleksandr Andriienko <oandriie@redhat.com>
@che-bot che-bot added status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. kind/enhancement A feature request - must adhere to the feature request template. labels Oct 9, 2019
@che-bot
Copy link
Contributor

che-bot commented Oct 9, 2019

E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:

@sleshchenko
Copy link
Member

ci-build

@che-bot
Copy link
Contributor

che-bot commented Oct 9, 2019

E2E tests of Eclipse Che Multiuser on OCP has failed:

@sleshchenko
Copy link
Member

ci-test

@che-bot
Copy link
Contributor

che-bot commented Oct 9, 2019

E2E tests of Eclipse Che Multiuser on OCP has failed:

@AndrienkoAleksandr AndrienkoAleksandr merged commit 36fe587 into master Oct 10, 2019
@AndrienkoAleksandr AndrienkoAleksandr deleted the usePluginBrokerWithCheTheiaRemoteRuntimeInjection branch October 10, 2019 07:08
@che-bot che-bot removed the status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. label Oct 10, 2019
@che-bot che-bot added this to the 7.3.0 milestone Oct 10, 2019
@musienko-maxim
Copy link
Contributor

The test failed because we got new changes from upstream and test is not been adapted yet. The same in master. I don't see regression in this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement A feature request - must adhere to the feature request template.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants