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

Show the warning message in the case with deprecated plugins #14707

Merged
merged 1 commit into from
Oct 8, 2019

Conversation

olexii4
Copy link
Contributor

@olexii4 olexii4 commented Sep 29, 2019

Signed-off-by: Oleksii Orel oorel@redhat.com

What does this PR do?

Add implementation of the warning message in the case with deprecated plugins and the possibility to auto-migrate plugins by pressing the button.

What issues does this PR fix or reference?

Needed for #13021

Release Notes

  • show a warning message in the case with deprecated editor or plugins.
  • add a possibility to migrate by pressing the button.

Docs PR

Screenshot from 2019-10-06 20-55-32
Screenshot from 2019-10-06 20-56-19

https://youtu.be/7U00YxALrFE

@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 Sep 29, 2019
@olexii4
Copy link
Contributor Author

olexii4 commented Sep 29, 2019

@slemeur WDYT?

@che-bot
Copy link
Contributor

che-bot commented Sep 29, 2019

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

  • build details
  • "che-server" docker image: maxura/che-server:14707

@che-bot
Copy link
Contributor

che-bot commented Sep 29, 2019

E2E tests of Eclipse Che Multiuser on OCP has failed:

@olexii4
Copy link
Contributor Author

olexii4 commented Sep 29, 2019

ci-test

@che-bot
Copy link
Contributor

che-bot commented Sep 29, 2019

E2E tests of Eclipse Che Multiuser on OCP has failed:

@slemeur
Copy link
Contributor

slemeur commented Oct 1, 2019

Is it migrating or upgrading ?

@olexii4
Copy link
Contributor Author

olexii4 commented Oct 1, 2019

I think it could be an upgrading in the case when we just upgrade the version of the same plugin. But it can be a migration too.

Copy link
Contributor

@amisevsk amisevsk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just to double-check, does the warning only appear on the Plugins tab, or whenever workspace details are opened?

@olexii4
Copy link
Contributor Author

olexii4 commented Oct 1, 2019

@amisevsk The warning only appears on the Plugins tab.

@amisevsk
Copy link
Contributor

amisevsk commented Oct 1, 2019

The warning only appears on the Plugins tab.

I think I understand why that is the case, but also worry that a user might never see it (I don't know how often a user would visit the plugins/editors tab for an already set up workspace).

+1 on the changes, regardless.

@olexii4
Copy link
Contributor Author

olexii4 commented Oct 3, 2019

I have updated
Screenshot from 2019-10-03 20-23-26
Screenshot from 2019-10-03 20-45-44
Screenshot from 2019-10-03 20-44-46

https://youtu.be/qkjxKXLGZ70

@olexii4
Copy link
Contributor Author

olexii4 commented Oct 3, 2019

@slemeur, @amisevsk WDYT?

@slemeur
Copy link
Contributor

slemeur commented Oct 4, 2019

Based on the video shared here: https://www.youtube.com/watch?v=qkjxKXLGZ70&feature=youtu.be

The workspace includes deprecated plugins. Migrate deprecated plugins by pressing the button Migrate plugins.

The workspace uses deprecated plugins. Upgrade the plugins to their latest version by pressing the button Upgrade plugins.

This plugin is deprecated. Migrate to the next .... version by pressing the icon

This is unclear. Which icon user has to press? It's a warning icon, a user will not expect to be able to click on it to fix the problem. I would remove the action from the button, and just explain what to do.
Message: "This plugin is deprecated. Select a newer version in the dropdown list or press "Upgrade plugins" to upgrade all plugins to their latest version".

For editors

  • The error message mention "Migrate plugins", but the button is not there.
  • Should the button be "Upgrade deprecated components"?

The workspace includes deprecated plugins and editors. Migrate deprecated plugins by pressing the button Migrate plugins.

The workspace uses deprecated plugins and editor. Upgrade to the latest versions available by pressing the button Upgrade plugins.

This workspace includes the deprecated editor
This workspaces uses a deprecated editor.

I find the experience a bit challenging and confusing for a end-user. Should the action be closer to the error message? Could you have "Click Here to upgrade all deprecated components" at the end of the error message, which will trigger the action ?

cc @evidolob .

@eclipse-che eclipse-che deleted a comment from che-bot Oct 7, 2019
@eclipse-che eclipse-che deleted a comment from che-bot Oct 7, 2019
@eclipse-che eclipse-che deleted a comment from che-bot Oct 7, 2019
@eclipse-che eclipse-che deleted a comment from che-bot Oct 7, 2019
@eclipse-che eclipse-che deleted a comment from che-bot Oct 7, 2019
@eclipse-che eclipse-che deleted a comment from che-bot Oct 7, 2019
@eclipse-che eclipse-che deleted a comment from che-bot Oct 7, 2019
@eclipse-che eclipse-che deleted a comment from che-bot Oct 7, 2019
@eclipse-che eclipse-che deleted a comment from che-bot Oct 7, 2019
@eclipse-che eclipse-che deleted a comment from che-bot Oct 7, 2019
@eclipse-che eclipse-che deleted a comment from che-bot Oct 7, 2019
@eclipse-che eclipse-che deleted a comment from che-bot Oct 7, 2019
@che-bot
Copy link
Contributor

che-bot commented Oct 7, 2019

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

@olexii4
Copy link
Contributor Author

olexii4 commented Oct 7, 2019

@slemeur Is it ok for you?

@che-bot
Copy link
Contributor

che-bot commented Oct 7, 2019

E2E tests of Eclipse Che Multiuser on OCP has been successful:

@che-bot
Copy link
Contributor

che-bot commented Oct 8, 2019

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

Signed-off-by: Oleksii Orel <oorel@redhat.com>
@che-bot
Copy link
Contributor

che-bot commented Oct 8, 2019

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

Copy link
Contributor

@akurinnoy akurinnoy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Nice work, Oleksii!

@che-bot
Copy link
Contributor

che-bot commented Oct 8, 2019

E2E tests of Eclipse Che Multiuser on OCP has failed:

@olexii4 olexii4 merged commit 70d0933 into master Oct 8, 2019
@olexii4 olexii4 deleted the CHE-13021 branch October 8, 2019 14:32
@che-bot che-bot added this to the 7.3.0 milestone Oct 8, 2019
@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 8, 2019
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.