Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

It's not possible to run a Task in Che-Code if it's not `che` type

See original GitHub issue

Describe the bug

If tasks.json file contains a task of non-che type (e.g. shell), it can’t be launched.

Che version

next (development version)

Steps to reproduce

Start a workspace with the Che-Code editor.
Run any non-che task defined in the tasks.json file.

Test tasks.json can be created with Terminal > Configure Tasks... > Create tasks.json file from template > maven.

Terminal panel is open, but the task is not run.

Expected behavior

A task should be run in a default (usually tools) container.

Runtime

OpenShift

Screenshots

Installation method

chectl/next

Environment

Linux

Release Notes Text

Tasks included in a tasks.json file of a type other than che were not loaded in a VS Code running in a Che workspace. This has been fixed in this release and tasks.json with tasks of any type are supported and loaded in a Che workspace.

Issue Analytics

State:
Created a year ago
Reactions:1
Comments:8 (7 by maintainers)

Top GitHub Comments

1reaction

l0rdcommented, Aug 17, 2022

@azatsarynnyy it looks like there is workaround: the task label should match the container name.

0reactions

azatsarynnyycommented, Oct 6, 2022

@l0rd yes, it’s done and we can close it. We restored the VS Code native terminal in Che-Code (https://github.com/che-incubator/che-code/pull/124). So, all task types supported by vanilla VS Code can now be run in Che-Code.