-
Notifications
You must be signed in to change notification settings - Fork 244
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
odo init
- welcoming messages
#5494
Comments
This was referenced Mar 3, 2022
Repository owner
moved this from In Progress
to Done
in odo v3-alpha1
Mar 7, 2022
This was referenced Mar 9, 2022
rm3l
added a commit
to rm3l/odo
that referenced
this issue
Mar 15, 2022
This relates to [1], because users might have similar symptoms (few seconds before any output) when running either `odo dev` or `odo deploy` in a source code directory with no Devfile, and those commands try to do an `Alyzer` analysis first. [1] redhat-developer#5494
rm3l
added a commit
to rm3l/odo
that referenced
this issue
Mar 15, 2022
This relates to [1], because users might have similar symptoms (few seconds before any output) when running either `odo dev` or `odo deploy` in a source code directory with no Devfile, and those commands try to do an Alizer analysis first. [1] redhat-developer#5494
3 tasks
rm3l
added a commit
to rm3l/odo
that referenced
this issue
Mar 16, 2022
This relates to [1], because users might have similar symptoms (few seconds before any output) when running either `odo dev` or `odo deploy` in a source code directory with no Devfile, and those commands try to do an Alizer analysis first. [1] redhat-developer#5494
openshift-merge-robot
pushed a commit
that referenced
this issue
Mar 18, 2022
This relates to [1], because users might have similar symptoms (few seconds before any output) when running either `odo dev` or `odo deploy` in a source code directory with no Devfile, and those commands try to do an Alizer analysis first. [1] #5494
3 tasks
cdrage
pushed a commit
to cdrage/odo
that referenced
this issue
Aug 31, 2022
…t-developer#5556) This relates to [1], because users might have similar symptoms (few seconds before any output) when running either `odo dev` or `odo deploy` in a source code directory with no Devfile, and those commands try to do an Alizer analysis first. [1] redhat-developer#5494
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
/kind task
I had issues with my connection and when I run
odo init
it took a few seconds before it showed any output.It looks like it is trying to do
Alizer
analysis as a first thing.There should be a message displayed first. So user is aware that odo is doing something
odo init
can run in two modes. In an empty directory. Or with directory with existing code.In empty directory the welcoming message should be something like:
With directory with source code:
links
one of the acceptance criteria in
odo init
- bootstrap new project in empty directory #5470odo init
- add ability to create component with existing codebase #5408The text was updated successfully, but these errors were encountered: