Composite command executes dependent commands in the same container

[RomanNikitenko]

Describe the bug

The composite command functionality does not take into account component field for dependent commands, for example, a composite command has the following dependent commands:

• command A has ubi8-based component
• command B has ubi9-based component

The composite command ignores component for dependent commands: commands A and B are always executed in the same container.

ubi8/ubi9 - just for example and testing, consider one command for DB container, another one to run a web app, or something else...

Che version

7.113@latest

Steps to reproduce

1. Start workspace https://che-dogfooding.apps.che-dev.x6e0.p1.openshiftapps.com/#https://github.com/RomanNikitenko/web-nodejs-sample/tree/composite-command
2. Terminal => Run task => run the following tasks:

• ubi8 container echo
• ubi9 container echo
• Parallel: Check echo ubi8-ubi9
• Sequential: Check echo ubi8-ubi9

3. Check output

Expected behavior

Dependent commands are executed in the own container

Screenshots

Environment

I've faced the problem on the dogfooding instance

[ibuziuk]

@RomanNikitenko good catch. just to clarify, this is not a regression, but a missing functionality?

[RomanNikitenko]

@ibuziuk
Composite command functionality was introduced in che-incubator/che-code#601.
The bug was present in the initial implementation ^.

I would say - we can consider it as a missing functionality, but I believe we should document this problem as a restriction for the composite command support that is going to be fixed in future.