[
https://issues.jboss.org/browse/JBIDE-23402?page=com.atlassian.jira.plugi...
]
Rob Stryker updated JBIDE-23402:
--------------------------------
Description:
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.
was:I can have a deploy pod is waiting for a build pod that already failed
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
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
(v6.4.11#64026)