Bug #2044: Aborted jobs(timeout) stop the buildflow. - Automated Build Generator - Open Source Collaboration Platform

Bug #2044

Aborted jobs(timeout) stop the buildflow.

Added by S. Meyer zu Borgsen over 9 years ago. Updated over 7 years ago.

Status:

Resolved

Start date:

10/07/2014

Priority:

Normal

Due date:

Assignee:

% Done:

100%

Category:

Target version:

0.5

Description

If one job gets aborted the buildflow does not continue.

                                xqilla-2.3.0-toolkit-robocup-trusty-tahr-nightly #2 completed  : ABORTED
                            }
ERROR: Failed to run DSL Script
java.util.concurrent.ExecutionException: org.codehaus.groovy.runtime.InvokerInvocationException: com.cloudbees.plugins.flow.JobExecutionFailureException

Associated revisions

Revision bf8c90b7
Added by J. Moringen over 9 years ago

buildflow ignores aborted builds in src/commandline-interface/main.lisp

fixes #2044

src/commandline-interface/main.lisp (configure-buildflow-job): ignore
ABORTED and better instead of FAILURE and better

History

#1 Updated by J. Moringen over 9 years ago

Status changed from New to Feedback

I don't think we can control what happens in case of timeouts. The buildflow is already configured to continue in case of errors by default.

#2 Updated by S. Meyer zu Borgsen over 9 years ago

If a timeout occurs for a job it gets the marked as ABORTED.
Failed jobs get the state FAILURE.
The problem is that it seems to only ignore the state FAILURE but not the state ABORTED.
This causes the whole buildflow to stop.

#3 Updated by J. Wienke over 9 years ago

The documentation states:

The flow will not take care of the triggered build status if it's better than the configured result. This allows you to ignore UNSTABLE < FAILURE < ABORTED.

So we could probably add an ignore(ABORTED).