-
Notifications
You must be signed in to change notification settings - Fork 111
Conversation
878903e
to
7937234
Compare
crw-ci-test |
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1) ℹ️ |
@tsmaeder Could you align your branch with master? |
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1) ℹ️ |
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1) ℹ️ |
22e83cb
to
36b3c8d
Compare
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1) ℹ️ |
@RomanNikitenko so what do we need for you to give me a +1 on this PR? |
@tsmaeder I reviewed and tested your last changes in upstream, so I think 2 problems from this comment should be fixed now. I didn't reject your changes, so you can merge this PR any time when you feel it's good enough. |
|
@tsmaeder Can you confirm that the following problems were fixed for
I guess with these changes we still have the following problems:
The first problem is quite critical from my point of view. |
crw-ci-test |
✅ E2E Happy path tests succeed 🎉 See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1) |
I had a (simple) fix for that one, but I guess when my Che on CRC stopped working, I must not have had pushed the fix, so it's lost now. I guess I'll have to redo it, then. |
These two are fixed with the latest upstream. |
crw-ci-test |
❌ 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 <[email protected]>
b310506
to
5a15ba5
Compare
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1) ℹ️ |
❌ 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 <[email protected]>
1bc1aa9
to
8240d76
Compare
@RomanNikitenko finally managed to fix the problem with executing from the "My Workspace" view. If you would be so kind to review that last commit? |
❌ 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 succeed 🎉 See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1) |
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.
Tested after update and can confirm that Running a che task from Workspace panel
was fixed within last commit - thanks!
I think the problem
Resolving variables for che tasks is not working at editing a configuration (user has open tasks.json file)
can be fixed in a separate PR.
btw: it makes sense to provide some changes to the doc https://www.eclipse.org/che/docs/che-7/defining-custom-commands-for-che-theia/ to inform user that |
What does this PR do?
This PR fixes:
The approach is to not replicate tasks to tasks.json but instead contributing them to the "tasks" key of the user preferences.
Update: switched to replicating the tasks, but to the user level.