[
https://issues.jboss.org/browse/JBIDE-24664?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-24664:
-------------------------------------
1) create a cdk server
2) Set a workspace 'oc' location
3) MAKE SURE $PATH does NOT have an 'oc' on it. Can test this via 'which
oc' and make sure not found.
4) via the created openshift connection, create a project, and an application
(eap-basic-s2i etc)
5) Create a server adapter once the app is created
6) Verify that publishing functions as expected.
This patch will end up re-opening
https://issues.jboss.org/browse/JBIDE-23862 (even
though it was already re-opened) because an underlying OC bug makes using spaces with oc
rsync impossible, so for now:
DO NOT consider the usecase of 'oc' with a space in it's path. This has not
worked and will not work until openshift origin fixes their bug.
Server adapter: unusable if oc is not on the path
-------------------------------------------------
Key: JBIDE-24664
URL:
https://issues.jboss.org/browse/JBIDE-24664
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.5.0.AM2
Reporter: Rob Stryker
Assignee: Dmitrii Bocharov
Priority: Critical
Labels: openshift_v3, server_adapter
Fix For: 4.5.0.AM2
The openshift rest client lib is not including the full path when calling ProcessBuilder.
So process builder is being asked to run a command named "oc" without the full
path to it. In such situation, the process builder (or the OS, not 100% sure which) will
revert to searching the system path for the given command, and choose the one on the
system path.
Since my machine does not have 'oc' on the system path, openshift tools cannot
run the oc command, or publish.
This also blocks adoption of JBIDE-24236, which allows users to select different OC. On
linux, the system path's OC will *always* be chosen, regardless of any user settings.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)