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

Set the editor content as an editor ID for custom editors #1038

Merged
merged 2 commits into from
Jan 16, 2024
Merged

Conversation

olexii4
Copy link
Contributor

@olexii4 olexii4 commented Jan 15, 2024

What does this PR do?

This PR fixed the problem with the wrong editor annotation for custom editors. It happens when we try to create a new workspace from the git repository with the custom editor in the .che directory.

For example:
Create a new workspace with the custom editor from the next link

{CHE-server}#https://github.com/olexii4/web-java-spring-boot.git

Check created devworkspace attributes with swagger

 {CHE-server}/dashboard/api/swagger

Знімок екрана 2024-01-16 о 17 31 20

We can see the wrong annotation "che.eclipse.org/che-editor": "che-incubator/che-code/latest" for che-idea.

What issues does this PR fix or reference?

Is it tested? How?

  1. Deploy Eclipse-Che with the image from this PR:
kubectl patch command
kubectl patch -n eclipse-che "checluster/eclipse-che" --type=json -p="[{"op": "replace", "path": "/spec/components/dashboard/deployment", "value": {containers: [{image: "quay.io/eclipse/che-dashboard:pr-1038", name: che-dashboard}]}}]"
  1. Create a new workspace with the custom editor from the next link
{CHE-server}#https://github.com/olexii4/web-java-spring-boot.git
  1. Check created devworkspace attributes with swagger
 {CHE-server}/dashboard/api/swagger

Знімок екрана 2024-01-16 о 17 51 51

We can see the custom editor content as che.eclipse.org/che-editor annotation.

Copy link

openshift-ci bot commented Jan 15, 2024

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@che-bot
Copy link
Contributor

che-bot commented Jan 15, 2024

Click here to review and test in web IDE: Contribute

Copy link

Docker image build succeeded: quay.io/eclipse/che-dashboard:pr-1038

kubectl patch command
kubectl patch -n eclipse-che "checluster/eclipse-che" --type=json -p="[{"op": "replace", "path": "/spec/components/dashboard/deployment", "value": {containers: [{image: "quay.io/eclipse/che-dashboard:pr-1038", name: che-dashboard}]}}]"

@openshift-ci openshift-ci bot removed the lgtm label Jan 16, 2024
@olexii4 olexii4 marked this pull request as ready for review January 16, 2024 14:10
@olexii4 olexii4 requested a review from ibuziuk as a code owner January 16, 2024 14:10
Copy link

Docker image build succeeded: quay.io/eclipse/che-dashboard:pr-1038

kubectl patch command
kubectl patch -n eclipse-che "checluster/eclipse-che" --type=json -p="[{"op": "replace", "path": "/spec/components/dashboard/deployment", "value": {containers: [{image: "quay.io/eclipse/che-dashboard:pr-1038", name: che-dashboard}]}}]"

@olexii4 olexii4 changed the title Set the editor content as an editor ID for the custom editors Set the editor content as an editor ID for custom editors Jan 16, 2024
@dmytro-ndp
Copy link
Contributor

/test v14-dashboard-happy-path

Copy link

openshift-ci bot commented Jan 16, 2024

@olexii4: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/v14-e2e-puppeteer 0be8d20 link true /test v14-e2e-puppeteer
ci/prow/v14-dashboard-happy-path 0be8d20 link true /test v14-dashboard-happy-path

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Copy link

openshift-ci bot commented Jan 16, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: akurinnoy, ibuziuk, olexii4

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@dmytro-ndp
Copy link
Contributor

/test v14-dashboard-happy-path

@olexii4 olexii4 merged commit 4d050a2 into main Jan 16, 2024
14 of 16 checks passed
@olexii4 olexii4 deleted the quick_fixes branch January 16, 2024 16:36
@devstudio-release
Copy link

Build 3.12 :: dashboard_3.x/442: Console, Changes, Git Data

@devstudio-release
Copy link

@devstudio-release
Copy link

@devstudio-release
Copy link

@devstudio-release
Copy link

@devstudio-release
Copy link

@devstudio-release
Copy link

Build 3.12 :: dashboard_3.x/442: SUCCESS

Upstream sync done; /DS_CI/sync-to-downstream_3.x/5961 triggered

@devstudio-release
Copy link

@devstudio-release
Copy link

@devstudio-release
Copy link

@devstudio-release
Copy link

@devstudio-release
Copy link

Build 3.12 :: sync-to-downstream_3.x/5963: SUCCESS

Build container: devspaces-operator-bundle synced; /DS_CI/get-sources-rhpkg-container-build_3.x/5828 triggered; /job/DS_CI/job/dsc_3.x triggered;

@devstudio-release
Copy link

Build 3.12 :: operator-bundle_3.x/2549: SUCCESS

Upstream sync done; /DS_CI/sync-to-downstream_3.x/5963 triggered

@devstudio-release
Copy link

Build 3.12 :: copyIIBsToQuay/2413: Console, Changes, Git Data

@devstudio-release
Copy link

Build 3.12 :: update-digests_3.x/5572: SUCCESS

Detected new images: rebuild operator-bundle
* dashboard; /DS_CI/operator-bundle_3.x/2549 triggered

@devstudio-release
Copy link

Build 3.12 :: dsc_3.x/1744: Console, Changes, Git Data

@devstudio-release
Copy link

Build 3.12 :: dsc_3.x/1744: SUCCESS

3.12.0-CI

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants