[
https://issues.jboss.org/browse/JBIDE-20117?page=com.atlassian.jira.plugi...
]
Marián Labuda edited comment on JBIDE-20117 at 6/19/15 1:38 AM:
----------------------------------------------------------------
I would say it is expected in some linear flow. But currently it looked for me, that there
are several pending builds and one running. I think the natural flow would be - if there
is no completed (successful) build, create a new build. If there is another running build
on a application, let this build be in state pending (another build should be from
different build config), If there is running build of the current build config, new build
should not be triggered. New build should be triggered once the build of current build
config is failed. What do you think? ;)
But I agree, it seems to me as upstream behaviour now.
was (Author: mlabuda):
I would say it is expected in some linear flow. But currently it looked for me, that there
are several pending builds and one running. I think the natural flow would be - if there
is no completed (successful) build, create a new build. If there is another running build
on a application, let this build be in state pending (another build should be from
different build config), If there is running build of the current build config, new build
should not be triggered. New build should be triggered once the build of current build
config is failed. What do you think? ;)
Explorer: new builds get triggered if I'm playing around in
OpenShift v3 connection tree
----------------------------------------------------------------------------------------
Key: JBIDE-20117
URL:
https://issues.jboss.org/browse/JBIDE-20117
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.0.Beta1
Reporter: Marián Labuda
Assignee: Jeff Cantrill
Labels: openshift_v3
Fix For: 4.3.0.Beta2
After I create an application from template and I play around with OpenShift v3
connection (expand tree items, collapse them, refresh resources, connection etc.) there
are several builds triggered, what should not be. Currently I do not know what exactly is
triggering builds, it's in state of investigating.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)