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

Devfile creation walkthroughs #18671

Closed
1 task done
l0rd opened this issue Dec 18, 2020 · 5 comments
Closed
1 task done

Devfile creation walkthroughs #18671

l0rd opened this issue Dec 18, 2020 · 5 comments
Labels
area/devfile-spec Issues related to Devfile v2 area/editor/theia Issues related to the che-theia IDE of Che area/editor/vscode Issues related to the Code OSS editor of Che area/plugins engine/devworkspace Issues related to Che configured to use the devworkspace controller as workspace engine. kind/enhancement A feature request - must adhere to the feature request template. kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. roadmap/6-months Epics that are planned to complete in the medium term (within 6 months)

Comments

@l0rd
Copy link
Contributor

l0rd commented Dec 18, 2020

Is your enhancement related to a problem? Please describe.

When a workspace is started and there is no Devfile in the project repository, we are not recommending to create one.

Describe the solution you'd like

We should recommend:

  • To use an existing stack (a (parent) devfile from the devfile registry)
  • To add container components (select image, endpoint, volumes etc...)
  • To include plugins (if the editor is che-theia or vscode)
  • To create and commit devfiles/extensions.json/che-theia-plugins.yaml in the project

Subtasks:

Additional context

This work should be included in the context of che workspaces that use the DevWorkspace operator, so that's not for v1 devfiles/plugins.

@l0rd l0rd added the kind/enhancement A feature request - must adhere to the feature request template. label Dec 18, 2020
@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 Dec 18, 2020
@l0rd l0rd added kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. area/editor/theia Issues related to the che-theia IDE of Che area/plugins engine/devworkspace Issues related to Che configured to use the devworkspace controller as workspace engine. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Dec 18, 2020
@l0rd l0rd added the roadmap/6-months Epics that are planned to complete in the medium term (within 6 months) label Mar 26, 2021
@sympatheticmoose sympatheticmoose added the area/devfile-spec Issues related to Devfile v2 label Mar 30, 2021
@l0rd l0rd changed the title Recommend to include a Devfile in projects that don't have one Guide creation of devfile when not present, for easier persistence and sharing of workspace definitions Mar 30, 2021
@l0rd
Copy link
Contributor Author

l0rd commented Sep 6, 2021

Let's put this one on hold. We may want to use the devfile library that should help generating a Devfile for a given repository.

@che-bot
Copy link
Contributor

che-bot commented Mar 5, 2022

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 Mar 5, 2022
@che-bot che-bot closed this as completed Mar 12, 2022
@l0rd
Copy link
Contributor Author

l0rd commented Mar 14, 2022

/remove-lifecycle stale

@l0rd l0rd reopened this Mar 14, 2022
@che-bot che-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 14, 2022
@che-bot
Copy link
Contributor

che-bot commented Sep 10, 2022

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 Sep 10, 2022
@che-bot che-bot closed this as completed Sep 17, 2022
@azatsarynnyy azatsarynnyy reopened this Dec 1, 2022
@azatsarynnyy azatsarynnyy added the area/editor/vscode Issues related to the Code OSS editor of Che label Dec 1, 2022
@che-bot che-bot closed this as completed Dec 8, 2022
@l0rd l0rd reopened this Dec 14, 2022
@l0rd l0rd removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 14, 2022
@l0rd l0rd changed the title Guide creation of devfile when not present, for easier persistence and sharing of workspace definitions Devfile creation walkthroughs Sep 6, 2023
@ibuziuk
Copy link
Member

ibuziuk commented Feb 8, 2024

@l0rd @vitaliy-guliy folks, can we close the issue? extension has been published

@ibuziuk ibuziuk closed this as completed Mar 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/devfile-spec Issues related to Devfile v2 area/editor/theia Issues related to the che-theia IDE of Che area/editor/vscode Issues related to the Code OSS editor of Che area/plugins engine/devworkspace Issues related to Che configured to use the devworkspace controller as workspace engine. kind/enhancement A feature request - must adhere to the feature request template. kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. roadmap/6-months Epics that are planned to complete in the medium term (within 6 months)
Projects
None yet
Development

No branches or pull requests

5 participants