Can not invoke Task if source is che

[gorkem]

If I have a task defined on tasks.json with source defined as che, it can not be started from Command palette. I can see a message printed on JS Console as ERROR Can't get task launch configuration for label: echo me

If I remove the source property from the following example task I can start the task without issues.

 {
            "label": "echo me",
            "source": "che",
            "type": "process",
            "command": "echo test",
            "target": {
                "machineName": "theia-idemh5"
            }
   }

[tsmaeder]

P2, because easy workaround.

[RomanNikitenko]

Should be fixed by eclipse-che/che-theia#295 for tasks from devfile, but I''ll check for the configuration from the description of the issue.

[RomanNikitenko]

• Theia runs tasks using the runner registered for the specified Task type or a default Task Runner if runner is not found for the task type.
  We register own runner to have ability to run tasks with type che. Our runner can run a task in a defined container.
• source - according to the doc - for a configured task it is the name of the root folder, while for a detected task, it is the name of the provider.

So for the task which we want to run using our runner in the specific container we should use "type": "che" and don't define source - the configuration is placed in config file, so source - is the name of the root folder and theia add source when reads the configuration from tasks.json file.

I added sleep 2 to the command as workaround for the issue. Please replace machineName for the correct value to test it. I saw in another issue your idea about mapping component to a container - thank you very much - I'll try it.

        {
            "label": "echo me",
            "type": "che",
            "command": "sleep 2 && echo test",
            "target": {
                "machineName": "theia-ide77o"
            }
        }

[gorkem]

@RomanNikitenko Is there a way we can omit source property when we carry a che provided task to task.json when we do a Configure Task command?

[RomanNikitenko]

For 7.0.0 we consider che tasks as configured, not as detected:

• we convert che commands from devfile to theia tasks format and copy them to tasks.json file of current workspace folder.

So user doesn't need to use Configure task action for che tasks. User can find all che tasks in
tasks.json file, edit them or add a new task.

tasks.json file can be open:

• manually
• by clicking cog icon (configure task action) from the Terminal > Run Task menu option
• from the Terminal > Configure Tasks menu

For detected task it opens tasks.json file and copies the configuration, but for configured one - just opens tasks.json file (config file already contains the configuration).

For master branch we have the corresponding PR. After merge the PR the behavior is the same as I described for 7.0.0.

[azatsarynnyy]

@RomanNikitenko could you please check if it's already fixed and whether we can close that issue

[RomanNikitenko]

Since the PR eclipse-che/che-theia#295 was merged we consider che tasks as configured, not as detected.
User doesn't need to use Configure task action for che tasks: we convert che commands from devfile to theia tasks format and copy them to tasks.json file.

So I'm closing the issue.