-
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
CHE-13476 improve CHE-6 workspaces warning #13506
Conversation
@slemeur WDYT? |
ci-test |
Results of automated E2E tests of Eclipse Che Multiuser on OCP: |
ci-test |
Results of automated E2E tests of Eclipse Che Multiuser on OCP: |
9627d95
to
5cf31fe
Compare
dashboard/src/app/workspaces/list-workspaces/workspace-item/workspace-item.controller.ts
Outdated
Show resolved
Hide resolved
ci-test |
Results of automated E2E tests of Eclipse Che Multiuser on OCP: |
ci-test |
Results of automated E2E tests of Eclipse Che Multiuser on OCP: |
Selenium tests execution on Eclipse Che Multiuser on OCP (https://ci.codenvycorp.com/job/che-pullrequests-test-ocp/1869//Selenium_20tests_20report/) doesn't show any regression against this Pull Request. |
@olexii4 What documentation it is pointing to? |
@slemeur I have added the link(in the description) |
Current state: waiting for the appropriate documentation to be merged. |
this.supportedRecipeTypeIssue = $sce.trustAsHtml('Current infrastructure doesn\'t support this workspace recipe type.'); | ||
|
||
this.supportedVersionTypeIssue = $sce.trustAsHtml(`This workspace is using old definition format which is not compatible anymore. | ||
Please follow the <a href="${cheBranding.getDocs().workspace}" target="_blank">documentation</a> |
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.
Would it be possible to reference the link to the doc section "Converting a Che 6 Workspace to a Che 7 devfile" ?
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.
Yes. It is possible. I have changed reference the link to the doc section "Converting a Che 6 Workspace to a Che 7 devfile"
2e2c2cc
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.
done
Signed-off-by: Oleksii Orel <oorel@redhat.com>
Signed-off-by: Oleksii Orel <oorel@redhat.com>
Not in the endgame but necessary to deploy Che 7 on che.osio. I am +1 to merge to master. |
ci-test |
Results of automated E2E tests of Eclipse Che Multiuser on OCP: |
Selenium tests execution on Eclipse Che Multiuser on OCP (https://ci.codenvycorp.com/job/che-pullrequests-test-ocp/1967/) doesn't show any regression against this Pull Request. |
Signed-off-by: Oleksii Orel oorel@redhat.com
What does this PR do?
Improve CHE-6 workspaces warning. Add a link in the pop-up warning message to the documentation, change font icon.
What issues does this PR fix or reference?
#13476
Release Notes
Docs PR
https://docs.google.com/document/d/1qrHg4F2FvTpafJAvgqgzeYTu6M0UA1mSjm_UCoQNFHc/edit?usp=sharing
https://youtu.be/2g9sdXLZQF8