Skip to content
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

Update commands' names #328

Merged
merged 3 commits into from Jul 30, 2020
Merged

Update commands' names #328

merged 3 commits into from Jul 30, 2020

Conversation

svor
Copy link
Contributor

@svor svor commented Jul 29, 2020

Signed-off-by: svor vsvydenk@redhat.com

What does this PR do?

  • Makes commands numbered from all devfiles in order they should be run.
  • Adds a new command to inform user to log into deployment cluster into devfiles which have 'deploy to Opneshift cluster' command

What issues does this PR fix or reference?

https://issues.redhat.com/browse/CRW-1046
https://issues.redhat.com/browse/CRW-1028

Signed-off-by: svor <vsvydenk@redhat.com>
@svor svor requested a review from nickboldt July 29, 2020 10:06
@svor svor self-assigned this Jul 29, 2020
@svor
Copy link
Contributor Author

svor commented Jul 29, 2020

@Ohrimenko1988 @dmytro-ndp do some automated tests depend on commands's names in CRW?

@svor svor requested a review from dmytro-ndp July 29, 2020 10:10
actions:
- workdir: '${CHE_PROJECTS_ROOT}/vertx-http-booster'
type: exec
command: >-
MAVEN_OPTS="-Xmx200m" && mvn fabric8:deploy -Popenshift -DskipTests
-Dvertx.disableDnsResolver=true
component: maven
- name: Debug remote java application
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should be 7. Debug...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nickboldt I didn't edit debug configuration commands because they aren't displayed in workspace view, so i don't see any reason to make them numbered

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did it for Che commands which are displayed in workspace view:
screenshot-codeready-crw-operatorhub-tls-oauth apps ocp44 crw-qe com-2020 07 30-10_06_09
The command which describes debug configuration has type vscode-launch which means that this configuration will be added into /projects/.theia/launch.json (it is NOT executable command)
screenshot-codeready-crw-operatorhub-tls-oauth apps ocp44 crw-qe com-2020 07 30-10_06_39
And the name of this command is displayed only in devfile, it is not visible in workspace.
Could you explain what is the reason to have

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah, apologies -- misunderstanding on my part w.r.t. command vs. config. :D

Signed-off-by: svor <vsvydenk@redhat.com>
actions:
- type: exec
component: dotnet
command: "dotnet build"
command: "dotnet run"
workdir: ${CHE_PROJECTS_ROOT}/dotnet-web-simple
-
name: Launch .NET Web Application on Debug mode
Copy link
Member

@nickboldt nickboldt Jul 29, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be numbered too? Or if not, then at least changed to

 Launch .net web application in debug mode

(to change from on to in, and be consistent with other "Initial upper case then lowercase" strings?)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

Signed-off-by: svor <vsvydenk@redhat.com>
@nickboldt nickboldt merged commit 79cf506 into redhat-developer:master Jul 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants