-
Notifications
You must be signed in to change notification settings - Fork 58
Add in CRUD actions for the devworkspace in dashboard #175
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
Conversation
Includes: - Creating, Listing, Starting, Stopping, Deleting Devworkspaces Signed-off-by: Josh Pinkney <joshpinkney@gmail.com>
Signed-off-by: Josh Pinkney <joshpinkney@gmail.com>
|
Code coverage diff between base branch:master and head branch: devworkspace-client2
|
|
✅ E2E dashboard-next tests succeed 🎉 See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1)
|
|
Docker image build succeeded: docker.io/maxura/che-server:che-dashboard-pull-175 |
Signed-off-by: Josh Pinkney <joshpinkney@gmail.com>
|
Code coverage diff between base branch:master and head branch: devworkspace-client2
|
|
✅ E2E dashboard-next tests succeed 🎉 See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1)
|
|
Docker image build succeeded: docker.io/maxura/che-server:che-dashboard-pull-175 |
sleshchenko
left a comment
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.
I tried to test with Docker image build succeeded: docker.io/maxura/che-server:che-dashboard-pull-175 on RHPDS but it did not work stably for me:
-
DevWorkspace displayed as Starting even if it's stopped or failed.


After sometime I was not able to reproduce it -
I was not able to create a devworkspace with devfile v2 if it does not have any component or command
schemaVersion: 2.0.0
metadata:
generateName: theia
Error: Failed to create a new workspace from the devfile: Cannot read property 'push' of undefined
- After DevWorkspace is removed on the cluster, it's still on the Dashboard (which is not really a bug but since we request each second, would be great if we're able to update dashboard state).
Signed-off-by: Josh Pinkney <joshpinkney@gmail.com>
|
Code coverage diff between base branch:master and head branch: devworkspace-client2
|
|
✅ E2E dashboard-next tests succeed 🎉 See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1)
|
|
Docker image build succeeded: docker.io/maxura/che-server:che-dashboard-pull-175 |
|
Code coverage diff between base branch:master and head branch: devworkspace-client2
|
|
✅ E2E dashboard-next tests succeed 🎉 See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1)
|
|
Docker image build succeeded: docker.io/maxura/che-server:che-dashboard-pull-175 |
|
❌ E2E dashboard-next tests failed ❗ See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1)
|
|
Code coverage diff between base branch:master and head branch: devworkspace-client2
|
|
Docker image build succeeded: docker.io/maxura/che-server:che-dashboard-pull-175 |
sleshchenko
left a comment
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.
Approving since it supports the flow which is needed for milestone 1:
- Create a workspace with custom workspace with devfile v2, or with factory flow.
- Propagate workspace status
- Open a workspace.
But we accept fact that some corner cases do not work, like edit workspace name (but UI don't forbid it).
Next step is propagate default plugins as DWT CRs in the same namespace where DW lives, since it's workflow we agreed on F2F and there is no plan to deploy DWT registry for milestone 1.
|
[dashboard-next-ci-test] |
I've created issue to handle missing pieces for milestone 1, feel free to comment or update if I'm missing something eclipse-che/che#19147 |
|
❌ E2E dashboard-next tests failed ❗ See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1)
|
Signed-off-by: Josh Pinkney <joshpinkney@gmail.com>
7ce566f to
9cff09a
Compare
|
❌ E2E dashboard-next tests failed ❗ See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1)
|
|
Code coverage diff between base branch:master and head branch: devworkspace-client2
|
|
Docker image build succeeded: docker.io/maxura/che-server:che-dashboard-pull-175 |
|
[dashboard-next-ci-test] |
sleshchenko
left a comment
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.
It must be ready to merge if it at least does not break dashboard when DevWorkspace is enabled. I'm testing it.
DevWorkspace can't be tested properly due a bug on DevWorkspace Che Operator, Lukas is taking a look.
|
❌ E2E dashboard-next tests failed ❗ See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1)
|
|
❌ E2E dashboard-next tests failed ❗ See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1)
|
|
Code coverage diff between base branch:master and head branch: devworkspace-client2
|
|
Docker image build succeeded: docker.io/maxura/che-server:che-dashboard-pull-175 |
5921240 to
9cff09a
Compare
|
Code coverage diff between base branch:master and head branch: devworkspace-client2
|
|
Code coverage diff between base branch:master and head branch: devworkspace-client2
|
|
✅ E2E dashboard-next tests succeed 🎉 See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1)
|
|
Docker image build succeeded: docker.io/maxura/che-server:che-dashboard-pull-175 |
1 similar comment
|
Docker image build succeeded: docker.io/maxura/che-server:che-dashboard-pull-175 |
sleshchenko
left a comment
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.
Dashboard on minikube works fine for me now.
Approving but it's needed to make sure Dashboard works fine on OpenShift with DevWorkspace support disabled.
|
I re-tested again with OpenShift and che.devworkspaces.enabled set to true and everything seemed working. I also tested with che.devworkspaces.enabled set to false on OpenShift and everything seemed to be working as well. I've created the last CQ's needed: https://dev.eclipse.org/ipzilla/show_bug.cgi?id=23110 and https://dev.eclipse.org/ipzilla/show_bug.cgi?id=23109 |
|
❌ E2E dashboard-next tests failed ❗ See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1)
|
What does this PR do?
This PR implements the basic of the CRUD (Create, read, update delete) actions in the dashboard for devworkspaces as well as a few other functionality.
Minor issues
Things to do
To test:
Install devworkspace-operator on the cluster:
git clone https://github.com/che-incubator/devworkspace-che-operator cd devworkspace-che-operator kubectl create namespace devworkspace-che make install deploy kubectl apply -n devworkspace-che -f ./samples/che-manager-openshift.yaml# then try dashboard kubectl get routesThen you can use: https://raw.githubusercontent.com/JPinkney/sample-devfile-repo/master/devfile.yaml as a sample devfile
You can also use: http://localhost:3333/#/load-factory/?url=https://github.com/JPinkney/sample-devfile-repo for simple factory
What issues does this PR fix or reference?
Fixes eclipse-che/che#18858
It also implement Factory flow eclipse-che/che#18846
Fixes eclipse-che/che#19147
Release Notes
Docs PR