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

Export current workspace definition as devfile #15400

Closed
1 task
slemeur opened this issue Dec 4, 2019 · 2 comments
Closed
1 task

Export current workspace definition as devfile #15400

slemeur opened this issue Dec 4, 2019 · 2 comments
Labels
area/editor/theia Issues related to the che-theia IDE of Che kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering.

Comments

@slemeur
Copy link
Contributor

slemeur commented Dec 4, 2019

Goal

The goal of this epic is to allow the user (developers using Eclipse Che) to export the current configuration of his workspace has a devfile.

As a user, I should be able to export my workspace as a devfile, so the workspace becomes reproducible and easy to share with other developers working on the same project than me.

Problems

Today, the workspace can get configured in many different ways.

  • It can be done from the IDE, to add tasks, commands, launch configs or plugins
  • It can be done from the dashboard, to add plugins or other settings

The problem is that none of those changes are easy to share and export in a devfile. The user has to go into the dashboard, on the devfile subtab for the workspace and then do a copy/paste somewhere, remove some fields and then he can finally add it to the project source code.

Proposed Solutions

Ability for the user to generate devfile from the editor
As a user in the editor, I want to get a menu action to allow exporting the current workspace configuration as a devfile. The devfile will be added to the project source code. If the devfile was already there, we will need to notify the user and inform that the current devfile will be overwritten.
This action should also be available from the command palette.

Ability for the user to sync the devfile from workspace pane
As a user, the workspace pane gives me a way to interact with the workspace components. I should be able to export the devfile from this panel as well.

Ability to export the devfile from the dashboard
As a user, I can go to the dashboard and see the workspace's configuration. It's a devfile, but a specific one, that I can't share to other users. We should allow to export the devfile to the user's clipboard, so he can easily share it.

Sub-tasks

@slemeur slemeur added the kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. label Dec 4, 2019
@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 4, 2019
@benoitf
Copy link
Contributor

benoitf commented Dec 5, 2019

hello, it looks like #12709

@benoitf benoitf added status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Dec 5, 2019
@benoitf benoitf added area/editor/theia Issues related to the che-theia IDE of Che team/editors and removed team/editors labels Jan 8, 2020
@che-bot
Copy link
Contributor

che-bot commented Jul 6, 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 Jul 6, 2020
@che-bot che-bot closed this as completed Jul 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/editor/theia Issues related to the che-theia IDE of Che kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering.
Projects
None yet
Development

No branches or pull requests

3 participants