Use 'containerName' instead of 'machineName' for che tasks

[RomanNikitenko]

The changes are the same as in the PR #367

What does this PR do?

Use 'containerName' instead of 'machineName' for che tasks

What issues does this PR fix or reference?

eclipse-che/che#13667

How to test

Use the component in your devfile

- 
    alias: theia-editor
    reference: >-
      https://raw.githubusercontent.com/RomanNikitenko/che-plugin-registry/master/v3/plugins/eclipse/che-theia/next/meta.yaml
    type: cheEditor

Use some command in your devfile, for example:

- name: che-theia:build
  actions:
  - type: exec
    component: che-dev
    command: >
              yarn
    workdir: /projects/che-theia

The component field defined for a command in a devfile should be converted into containerName (not machineName) field for a task configuration in a tasks.json file when a workspace has started.

Signed-off-by: Roman Nikitenko rnikiten@redhat.com

[sleshchenko]

Is it still relevant? I mean that there is another issue to use component instead. Or it will be the next step?

[vparfonov]

Is it still relevant? I mean that there is another issue to use component instead. Or it will be the next step?

yes, it will be next step. With this PR we align with 7.0 version

[RomanNikitenko]

@sleshchenko
You are right - we are going to use component instead of machineName, but we are not ready for it and we have the corresponding issue.
So I would like to align the behavior for master branch with 7.0.0 and we can improve it when the corresponding issue is resolved.

[RomanNikitenko]

I had to force-push the same changes to restart ci-build.

[sleshchenko]

Thanks for answering my question.