[jbosstools-issues] [JBoss JIRA] (JBIDE-23819) Unable to determine oc 1.4.0 version
Andre Dietisheim (JIRA)
issues at jboss.org
Wed Feb 1 18:13:00 EST 2017
[ https://issues.jboss.org/browse/JBIDE-23819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13357081#comment-13357081 ]
Andre Dietisheim commented on JBIDE-23819:
------------------------------------------
The problem is that the regex, that's responsible for the detection of the oc version is bad.
In order to detect the version, "oc version" is run by the tooling.
I downloaded all oc binaries that exist currently and inspected the outputs.
Here they are
* oc binaries available from github:
{code}
oc v1.5.0-alpha.2+e4b43ee
oc v1.5.0-alpha.1+71d3fa9
oc v1.5.0-alpha.0+3b2bbe5
oc v1.4.1+3f9807a
oc v1.4.0+208f053
oc v1.4.0-rc1+b4e0954
oc v1.4.0-alpha.1+f189ede
oc v1.3.3
oc v1.3.2
oc v1.2.2
{code}
* oc (enterprise) binaries available from access.redhat.com:
{code}
oc 2 v3.4.1.2
oc 2 v3.4.0.40
oc 2 v3.4.0.39
oc 2 v3.3.1.7
oc 2 v3.3.1.5
oc 2 v3.3.1.4
oc 2 v3.3.1.3
{code}
> Unable to determine oc 1.4.0 version
> ------------------------------------
>
> Key: JBIDE-23819
> URL: https://issues.jboss.org/browse/JBIDE-23819
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.AM2
> Environment: Devstudio 10.3.0.AM2, oc client v1.4.1 downloaded from https://github.com/openshift/origin/releases/tag/v1.4.1
> Reporter: Radim Hopp
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: oc_binary, openshift_v3
> Fix For: 4.4.3.Final
>
> Attachments: oc-14-not-recognized.png
>
>
> Selecting oc version 1.4.1 [1] in OpenShift 3 preferences dialog results in "Could not determine your OpenShift client version".
> [1] - https://github.com/openshift/origin/releases/tag/v1.4.1
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the jbosstools-issues
mailing list