[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-8425) add capability to chain jobs so that successor jobs dont get executed if predecessors are canceled / fail

[Rob Stryker (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-8425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Stryker resolved JBIDE-8425.
--------------------------------

    Resolution: Rejected


ChainedJob already includes this functionality

		if (nextJob != null && status != null && status.getSeverity() != IStatus.ERROR
				&& status.getSeverity() != IStatus.CANCEL)
			nextJob.schedule();


> add capability to chain jobs so that successor jobs dont get executed if predecessors are canceled / fail
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-8425
>                 URL: https://issues.jboss.org/browse/JBIDE-8425
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: deltacloud
>    Affects Versions: 3.2.0.CR1
>            Reporter: Andre Dietisheim
>            Assignee: Andre Dietisheim
>            Priority: Minor
>             Fix For: 3.3.x
>
>
> The current implementation of ChainedJob chains jobs so that all of them are executed regardless if the predecessors are canceled or fail.
> In the context of deltacloud there's no need to create an RSE (successor job) if launching the instance (predecessor job) was canceled/failed. There's no way for the RSE creation job to know if the launch was canceled/failed. It may only guess so if the instance is null or has no hostname.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira