[jbosstools-issues] [JBoss JIRA] (JBIDE-24884) Log an error if detected cdk registry is wrong

[Martin Malina (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-24884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453443#comment-13453443 ] 

Martin Malina commented on JBIDE-24884:
---------------------------------------

That seems reasonable. I will verify this in time.

> Log an error if detected cdk registry is wrong
> ----------------------------------------------
>
>                 Key: JBIDE-24884
>                 URL: https://issues.jboss.org/browse/JBIDE-24884
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: cdk, openshift
>    Affects Versions: 4.5.1.AM1
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>             Fix For: 4.5.1.AM1
>
>
> This is a followup of JBIDE-24783.
> When minishift openshift registry is unable to return a valid registry, the tooling should log an error. JBIDE-24783 was supposed to add this thing (along with removing the default value), but I was not able to trigger the error.
> The workflow is:
> Once cdk is started in eclipse, the cdk tooling will create the openshift connection and run minishift openshift registry to figure out which registry to use. But in my testing even if this returns "bla bla", the tooling will happily accept it.
> To test this, you can use a simple minishift wrapper such as this:
> {code}
> #!/bin/bash
> case $* in
> "openshift registry")
> 	echo bla bla
> 	exit 1
> 	;;
> *)
> 	/Users/rasp/jbossqa/cdk/cdk-3.1.0/minishift $*
> esac
> {code}
> You can also remove the "exit 1" to check what happens with zero exit code.
> In my opinion any of these should trigger an error:
> a) minishift openshift registry finishes with a non-zero code
> b) the returned string is not a valid url



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)