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

Support compound che tasks #15542

Open
RomanNikitenko opened this issue Dec 19, 2019 · 2 comments
Open

Support compound che tasks #15542

RomanNikitenko opened this issue Dec 19, 2019 · 2 comments
Labels
area/plugins kind/enhancement A feature request - must adhere to the feature request template. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. severity/P1 Has a major impact to usage or development of the system.

Comments

@RomanNikitenko
Copy link
Member

RomanNikitenko commented Dec 19, 2019

Is your enhancement related to a problem? Please describe.

Recently theia started to support compound tasks.
Please see https://code.visualstudio.com/docs/editor/tasks#_compound-tasks for more details.

I tested the corresponding PR to theia project to investigate the influence on che tasks.
So, for example, if you have some build task which depends on subTask_1 and subTask_2:

  • subTask_1 is started
  • subTask_1 is completed
  • subTask_2 is started
  • subTask_2 is completed
  • the task build is started

Also user has ability to define order for sub tasks: sequence or parallel

Please see a short demo for the current state of che tasks: https://youtu.be/zhHkAunnAp0

Looks like in general it works for che tasks, but some adaptation is required on che-theia side

Describe the solution you'd like

We need at least:

  • add the corresponding fields to the che task schema to get working the content assistant for new fields
  • update the documentation for che tasks
  • at the moment compound tasks work from Terminal => Run Task menu, but don't work from Workspace panel
@RomanNikitenko RomanNikitenko added the kind/enhancement A feature request - must adhere to the feature request template. label Dec 19, 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 19, 2019
@tolusha tolusha added area/plugins severity/P1 Has a major impact to usage or development of the system. team/plugins and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Dec 20, 2019
@azatsarynnyy azatsarynnyy mentioned this issue Dec 20, 2019
8 tasks
@che-bot
Copy link
Contributor

che-bot commented Jun 17, 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 Jun 17, 2020
@RomanNikitenko RomanNikitenko removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 17, 2020
@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
@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.

@ericwill ericwill 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/plugins kind/enhancement A feature request - must adhere to the feature request template. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

5 participants