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.

Sign up for GitHub

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

Jump to bottom

Document how to develop Che (wsmaster) in Che #14183

Open
mmorhun opened this issue Aug 9, 2019 · 7 comments
Open

Document how to develop Che (wsmaster) in Che #14183

mmorhun opened this issue Aug 9, 2019 · 7 comments
Assignees
@skabashnyuk
Labels
area/doc Issues related to documentation kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. severity/P2 Has a minor but important impact to the usage or development of the system.

Comments

@mmorhun
Copy link
Contributor

mmorhun commented Aug 9, 2019

We should provide and have documented flow of Che development inside Che workspace.
@mmorhun mmorhun added the kind/task Internal things, technical debt, and to-do tasks to be performed. label Aug 9, 2019
@mmorhun
Copy link
Contributor Author

mmorhun commented Aug 9, 2019

Would be nice to include:

  • devfile for the workspace with all the tooling for development
  • commands to build Che master
  • instructions how to run/debug specific test or tests from a module
  • a way to build Che master image
  • guide how to run second Che master and test it (would be great to be able to start workspaces from that instance)
  • instructions how to debug second Che master

We may add some requirement for cluster in which main Che is run, for example to own second namespace, etc.

@mmorhun mmorhun mentioned this issue Aug 9, 2019
Closed
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Aug 9, 2019
@rhopp rhopp added this to the 7.1.0 milestone Aug 9, 2019
@rhopp rhopp added severity/P2 Has a minor but important impact to the usage or development of the system. area/doc Issues related to documentation and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Aug 9, 2019
@sunix
Copy link
Contributor

sunix commented Aug 9, 2019

Could we name it che-wsmaster in che ? or something like that because we have many pieces in Che and you are focussing on wsmaster

@gorkem gorkem changed the title Create and document Che in Che flow Create a document Che (wsmaster) in Che flow Aug 11, 2019
@che-bot
Copy link
Contributor

che-bot commented Feb 12, 2020

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.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 12, 2020
@mmorhun mmorhun removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 13, 2020
@l0rd l0rd removed this from the 7.1.0 milestone Jul 8, 2020
@l0rd l0rd changed the title Create a document Che (wsmaster) in Che flow Document how to develop Che (wsmaster) in Che Jul 8, 2020
@che-bot
Copy link
Contributor

che-bot commented Jan 4, 2021

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.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 4, 2021
@skabashnyuk skabashnyuk added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 5, 2021
@yhontyk
Copy link

yhontyk commented Jan 29, 2021

Docs Jira issue https://issues.redhat.com/browse/RHDEVDOCS-2579

@pmkovar
Copy link

pmkovar commented Jun 15, 2021

@skabashnyuk Do you want to self-assign this?

@skabashnyuk skabashnyuk self-assigned this Jun 15, 2021
@themr0c themr0c removed the team/doc label Jun 7, 2022
@themr0c
Copy link
Contributor

themr0c commented Jun 7, 2022

@l0rd should we keep this task open?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@skabashnyuk skabashnyuk

Labels
area/doc Issues related to documentation kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. severity/P2 Has a minor but important impact to the usage or development of the system.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
9 participants
@themr0c @pmkovar @l0rd @sunix @rhopp @skabashnyuk @mmorhun @yhontyk @che-bot