Some devfiles have several commands that need to be executed in a precise order to succeed.
Some are named with prefixed numbers that help the user, but some others are not.
For instance:
angular
python-django
Che version
latest
nightly
other: please specify
Steps to reproduce
start the Django Python devfile
open my workspace view
start the first command: install dependencies
it fails sh: 1: .: Can't open /projects/.venv/bin/activate
Expected behavior
the commands should be prefixed with numbers that would tell which one to start. in this case, user should execute the command set up venv first, but it is listed in alphabetical order: at the end.
Runtime
kubernetes (include output of kubectl version)
Openshift (include output of oc version)
minikube (include output of minikube version and kubectl version)
minishift (include output of minishift version and oc version)
docker-desktop + K8S (include output of docker version and kubectl version)
other: (please specify)
Screenshots
Installation method
chectl
provide a full command that was used to deploy Eclipse Che (including the output)
provide an output of chectl version command
OperatorHub
I don't know
Environment
my computer
Windows
Linux
macOS
Cloud
Amazon
Azure
GCE
other (please specify)
Dev Sandbox (workspaces.openshift.com)
other: please specify
Eclipse Che Logs
Additional context
The text was updated successfully, but these errors were encountered:
Also it would be nice to see the list of examples that have this problem in this issue. We could make it an epic. Adding n&n label anyway as that has a important impact on UX, especially for new users.
Describe the bug
Some devfiles have several commands that need to be executed in a precise order to succeed.
Some are named with prefixed numbers that help the user, but some others are not.
For instance:
Che version
Steps to reproduce
install dependenciessh: 1: .: Can't open /projects/.venv/bin/activateExpected behavior
the commands should be prefixed with numbers that would tell which one to start. in this case, user should execute the command
set up venvfirst, but it is listed in alphabetical order: at the end.Runtime
kubectl version)oc version)minikube versionandkubectl version)minishift versionandoc version)docker versionandkubectl version)Screenshots
Installation method
chectl versioncommandEnvironment
Eclipse Che Logs
Additional context
The text was updated successfully, but these errors were encountered: