che
che copied to clipboard
How to contribute
Summary
I want to know how run che in debug mode and see internal working.
This description is old and does not work, commands do not exist, dev file links are broken https://github.com/eclipse/che/blob/master/CONTRIBUTING.md
Relevant information
Just provide a plain exmplanation how your development environment is set up , so I can mimick it.
Related sub-tasks
- [ ] https://github.com/eclipse/che/issues/21363
Hello @tsadigovAgmail The steps are the following:
- Update CheCluster CR:
spec.server.cheDebug: true
- Forward debug port:
chectl server:debug
- Connect to a
localhost:8000
to debug a remote Che server
Thanks @tolusha for the answer. I am sure for a gifted person like you this might be the answer. But for non gifted person like me this seems to be not enough. So I cant agree @ibuziuk here. I dont see how it provides alternative information to this doc https://github.com/eclipse/che/blob/master/CONTRIBUTING.md
Which subproject is this endpoint representing? Which platform is it built on? Even maybe how you set up the IDE? I think kind of onboarding instructions would be great. How do you provide an environment to a new member?
CONTRIBUTING.md file mentiones this
$ chectl workspace:start -f https://raw.githubusercontent.com/eclipse/che-theia/main/devfiles/che-theia-all.devfile.yaml or https://<CheInstance>/f?url=https://raw.githubusercontent.com/eclipse/che-theia/main/devfiles/che-theia-all.devfile.yaml
as mentionned above the command does not exist - chectl workspace:start But I can try using the devfile from my che installation. And there I see the devfile link is broken. ` Searching in commit history I found the file and also noticed generic change where XYZ-all.devfile.yaml files renamed to XYZ-dev.devfile.yaml which is not reflected in CONTRIBUTING.md and .repositories.yaml files.
So @Divine1 you may try just replacing all->dev in devfile names and try that way. Lets see how it goes from that point.
https://<CheInstance>/f?url=https://raw.githubusercontent.com/eclipse/che-theia/main/devfiles/che-theia-dev.devfile.yaml
Here is what I got, I am trying the commands with varying degree of success. Will go over doc again to see if I need to do any setup.
@tsadigovAgmail thank you.
normally i would like to do trail and error
approach but i'm stuck with another issue related to setting up eclipse che on k8s cluster, the issue detail is present in this link https://github.com/eclipse/che/issues/21404 .
i will verify your recommended approach once i find solution for the issue (https://github.com/eclipse/che/issues/21404)
Issues go stale after 180
days of inactivity. lifecycle/stale
issues rot after an additional 7
days of inactivity and eventually close.
Mark the issue as fresh with /remove-lifecycle stale
in a new comment.
If this issue is safe to close now please do so.
Moderators: Add lifecycle/frozen
label to avoid stale mode.