[jbosstools-issues] [JBoss JIRA] (JBIDE-23402) [WATCHER] Explorer: can "Deploy Latest" even if the build failed

[Andre Dietisheim (JIRA)]

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

Andre Dietisheim edited comment on JBIDE-23402 at 11/23/16 10:48 AM:
---------------------------------------------------------------------

[~rob.stryker] dare to file an issue against origin since you have the most infos?


was (Author: adietish):
[~rob.stryker] dare to file an issue again origin since you have the most infos?

> [WATCHER] Explorer: can "Deploy Latest" even if the build failed
> ----------------------------------------------------------------
>
>                 Key: JBIDE-23402
>                 URL: https://issues.jboss.org/browse/JBIDE-23402
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift, upstream
>    Affects Versions: 4.4.2.AM2
>            Reporter: Andre Dietisheim
>             Fix For: 4.4.x
>
>         Attachments: JBIDE-23402-a.png, JBIDE-23402-b.png
>
>
> When right-clicking on an application, we can select "Deploy Latest".  This will start both a build and a deploy pod. The deploy pod will wait for the build pod to complete. 
> In this case, due to github being unavailable, the build pod will fail very quickly. The deploy pod will then continue waiting up to 10 minutes even though what it is waiting for has already failed.  This 10 minutes is wasted. It should fail quickly. 



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