16502 refactor rpcprotocol#971
Conversation
|
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1)
|
6f79c05 to
e6d147d
Compare
|
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1)
|
|
Since I have two thumbs up on the upstream PR, I'm removing the "draft" status, Reviewers, please review! |
azatsarynnyy
left a comment
There was a problem hiding this comment.
The code looks good to me, as it's just an adaptation to the upstream refactoring.
Let us know once a Che-Theia image is ready for testing the PR.
|
|
||
| @postConstruct() | ||
| protected postConstruct(): void { | ||
| console.log('hosted plugin remote postconstruct'); |
There was a problem hiding this comment.
Do we need to keep this log or it's just a leftover?
I honestly don't know how to create one: the Github action PR checks don't publish images and the "happy path" CI job doesn't have the ability to work with Theia branches. 🤷 I guess self-hosting is the process to test in this case. |
|
@tsmaeder you could change in build.include file the branch used |
|
Hmh...does the plugin-host executable get rebuilt when we rebuild the che-theia image? Not sure anymore. Because the protocol between back-end and plugin host changed. @benoitf what would be the right way to test that? |
|
@tsmaeder yes it builds the endpoint image as well Right way: tune build.include to include remote upstream theia branch/fork instead of eclipse-theia/theia + master so Happy path will deploy both custom theia and custom theia endpoint (so it will validate if communication across containers/VS Code extensions works fine) |
e6d147d to
20976ee
Compare
|
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1)
|
|
[crw-ci-test] |
|
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1)
|
|
[crw-ci-test --rebuild] |
|
✅ E2E Happy path tests succeed 🎉 See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1)
|
|
@benoitf @azatsarynnyy we have an image being built now. Could you test, please? |
|
let's merge it after 7.28.0 is tagged (ie: for 7.29.0 so it'll be a new CRW/Che lifecycle) |
20976ee to
939dce4
Compare
|
✅ E2E Happy path tests succeed 🎉 See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1)
|
|
@tsmaeder what's the status of this PR? |
|
When I get a moment, I need to rebase the upstream PR before I can merge both. |
|
now, we're at 2/3 of the sprint (my previous comment was 3 weeks ago) so it's not becoming a good time to merge refactoring upstream/downstream stuff |
939dce4 to
0fc4429
Compare
|
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1)
|
250ef27 to
52d25d9
Compare
|
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1)
|
Signed-off-by: Thomas Mäder <tmader@redhat.com>
Signed-off-by: Thomas Mäder <tmader@redhat.com>
52d25d9 to
467ae97
Compare
|
✅ E2E Happy path tests succeed 🎉 See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1)
|
|
[crw-ci-test --rebuild] |
|
✅ E2E Happy path tests succeed 🎉 See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1)
|
Signed-off-by: tsmaeder <tmader@redhat.com>
|
✅ E2E Happy path tests succeed 🎉 See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1)
|
Signed-off-by: tsmaeder <tmader@redhat.com>
Codecov Report
@@ Coverage Diff @@
## master #971 +/- ##
==========================================
+ Coverage 29.45% 31.50% +2.04%
==========================================
Files 277 278 +1
Lines 9336 9469 +133
Branches 1380 1419 +39
==========================================
+ Hits 2750 2983 +233
+ Misses 6487 6484 -3
+ Partials 99 2 -97
Continue to review full report at Codecov.
|
|
✅ E2E Happy path tests succeed 🎉 See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1)
|
What does this PR do?
This PR adapts che-theia to the upstream PR eclipse-theia/theia#8972. As such, I'll leave it in draft PR staus until upstream is merged. It is still open for review.
What issues does this PR fix or reference?
This is a refactoring and as such not related to a PR. See upstream PR for justification.
How to test this PR?
Use local and remote plugins in a workspace based on the results of this PR build. (self-hosting or via the image built for the happy-path tests.
PR Checklist
As the author of this Pull Request I made sure that:
What issues does this PR fix or referenceandHow to test this PRcompletedReviewers
Reviewers, please comment how you tested the PR when approving it.
Happy Path Channel
HAPPY_PATH_CHANNEL=next