Change way of storage runtime info for che tasks

[RomanNikitenko]

What does this PR do?

Improves the way of storage runtime info for Che tasks.

We keep runtime info for Che tasks on plugin side. The problem is the plugin side is reloaded each time the browser refreshes and we lose runtime info at this step. For more details please see eclipse-che/che#13722 (comment).

The changes suggest to store runtime info on node side of eclipse-che/theia-plugin-ext.

What issues does this PR fix or reference?

eclipse-che/che#13722

How to test

The changes are related to che tasks, so please try to run any che task from My Workspace panel and from Terminal -> Run Task menu as well

Signed-off-by: Roman Nikitenko [email protected]

[che-bot]

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

• build details
• "che-theia" docker image: maxura/che-theia:419
• test artifacts
• https://github.com/orgs/eclipse/teams/eclipse-che-qa please check this report.
  Use command "crw-ci-test" to rerun the test.

[che-bot]

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

• build details
• "che-theia" docker image: maxura/che-theia:419

[che-bot]

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

• build details
• "che-theia" docker image: maxura/che-theia:419

[che-bot]

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

• build details
• test report
• logs and configs
• "che-theia" docker image: maxura/che-theia:419
• "che-theia-endpoint-runtime" docker image: maxura/che-theia-endpoint-runtime:419
• "che-remote-plugin-runner-java8" docker image: maxura/che-remote-plugin-runner-java8:419
• "che-remote-plugin-kubernetes-tooling-1.0.0" docker image: maxura/che-remote-plugin-kubernetes-tooling-1.0.0:419
• Happy path tests DevFile
• https://github.com/orgs/eclipse/teams/eclipse-che-qa please check this report.
  Use command "crw-ci-test" to rerun the test.

[che-bot]

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

• build details
• test report
• logs and configs
• "che-theia" docker image: maxura/che-theia:419
• "che-theia-endpoint-runtime" docker image: maxura/che-theia-endpoint-runtime:419
• "che-remote-plugin-runner-java8" docker image: maxura/che-remote-plugin-runner-java8:419
• "che-remote-plugin-kubernetes-tooling-1.0.0" docker image: maxura/che-remote-plugin-kubernetes-tooling-1.0.0:419
• Happy path tests DevFile
• https://github.com/orgs/eclipse/teams/eclipse-che-qa please check this report.
  Use command "crw-ci-test" to rerun the test.

[che-bot]

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

• build details
• test report
• logs and configs
• "che-theia" docker image: maxura/che-theia:419
• "che-theia-endpoint-runtime" docker image: maxura/che-theia-endpoint-runtime:419
• "che-remote-plugin-runner-java8" docker image: maxura/che-remote-plugin-runner-java8:419
• "che-remote-plugin-kubernetes-tooling-1.0.0" docker image: maxura/che-remote-plugin-kubernetes-tooling-1.0.0:419
• Happy path tests DevFile
• https://github.com/orgs/eclipse/teams/eclipse-che-qa please check this report.
  Use command "crw-ci-test" to rerun the test.

[che-bot]

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

• build details
• test report
• logs and configs
• "che-theia" docker image: maxura/che-theia:419
• "che-theia-endpoint-runtime" docker image: maxura/che-theia-endpoint-runtime:419
• "che-remote-plugin-runner-java8" docker image: maxura/che-remote-plugin-runner-java8:419
• "che-remote-plugin-kubernetes-tooling-1.0.0" docker image: maxura/che-remote-plugin-kubernetes-tooling-1.0.0:419
• Happy path tests DevFile
• https://github.com/orgs/eclipse/teams/eclipse-che-qa please check this report.
  Use command "crw-ci-test" to rerun the test.

[che-bot]

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

• build details
• test report
• logs and configs
• "che-theia" docker image: maxura/che-theia:419
• "che-theia-endpoint-runtime" docker image: maxura/che-theia-endpoint-runtime:419
• "che-remote-plugin-runner-java8" docker image: maxura/che-remote-plugin-runner-java8:419
• "che-remote-plugin-kubernetes-tooling-1.0.0" docker image: maxura/che-remote-plugin-kubernetes-tooling-1.0.0:419
• Happy path tests DevFile
• https://github.com/orgs/eclipse/teams/eclipse-che-qa please check this report.
  Use command "crw-ci-test" to rerun the test.

[RomanNikitenko]

crw-ci-test

[che-bot]

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

• build details
• logs and configs
• "che-theia" docker image: maxura/che-theia:419
• "che-theia-endpoint-runtime" docker image: maxura/che-theia-endpoint-runtime:419
• "che-remote-plugin-runner-java8" docker image: maxura/che-remote-plugin-runner-java8:419
• "che-remote-plugin-kubernetes-tooling-1.0.0" docker image: maxura/che-remote-plugin-kubernetes-tooling-1.0.0:419
• Happy path tests DevFile

[sunix]

The changes are related to che tasks, so please try to run any che task from My Workspace panel and from Terminal -> Run Task menu as well

So this is working without your changes. So this is refactoring right ?

[RomanNikitenko]

The changes are related to che tasks, so please try to run any che task from My Workspace panel and from Terminal -> Run Task menu as well

So this is working without your changes. So this is refactoring right ?

This is refactoring which allows to not lose runtime info at page refreshing.