[jbosstools-issues] [JBoss JIRA] (JBIDE-14354) I dont get credentials reported when I create a jenkins initially (when creating an app) (WATCHER ISSUE)

[RH Bugzilla Integration (JIRA)]

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

RH Bugzilla Integration commented on JBIDE-14354:
-------------------------------------------------

Andre Dietisheim <adietish at redhat.com> made a comment on [bug 958113|https://bugzilla.redhat.com/show_bug.cgi?id=958113]

Talking to Abishek and further investigating I found out that the problem is not in the broker but in JBoss Tools. 
It is caused by a background thread that is responsible for creating the application but timeouts. It would then refresh to make sure the application wasn't created yet and keep trying to create it otherwise. 
Apparently the issue started to appear when the timing on OpenShift further degraded. I was somehow fooled by the requests I catched, sorry!
                
> I dont get credentials reported when I create a jenkins initially (when creating an app) (WATCHER ISSUE)
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-14354
>                 URL: https://issues.jboss.org/browse/JBIDE-14354
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: openshift
>    Affects Versions: 4.1.0.Alpha2
>            Reporter: Andre Dietisheim
>            Assignee: Andre Dietisheim
>            Priority: Critical
>             Fix For: 4.1.x
>
>         Attachments: correct-creation-log.png, no-information-from-openshift.png, null-creation-log.png
>
>
> # EXEC: launch the OpenShift application wizard
> # EXEC: in the embedded cartridges, check jenkins-client
> # ASSERT: you get a dialog that tells you that you have to create a jenkins application
> # EXEC: hit "Apply"
> # ASSERT: you get prompted to provide a name for the jenkins application
> # EXEC: provide some name
> # ASSERT: wait until you get the creation log presented in a dialog
> Result:
> The dialogs shows *null*
> !null-creation-log.png!
> Expected:
> The creation log dialog prints the IP, username and password for your jenkins instance
> !correct-creation-log.png!
> Workaround:
> * embed jenkins-client afterwards by picking *Edit Embeddable Cartridges* in the context menu of your application in the OpenShift Explorer
> =OR=
> * look the credentials up in the environment variables by picking *Environament Variables* in the context menu of your application in OpenShift Explorer

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira