Issue Type: Improvement Improvement
Assignee: Nicolas De Loof
Components: build-flow
Created: 30/Nov/12 11:15 AM
Description:

The user should be able to configure behaviour when a failure occurs. Currently all following jobs are skipped.

In some cases this is the correct behaviour, e.g.:

B depends on A, so if A fails we want to skip B
parallel(
  { build("A"); build("B"); },
  { build("C"); }
)

In other cases we always want to run a job, e.g.:

Always run CLEANUP, even if A, B or C fails
parallel(
  { build("A"); build("B"); },
  { build("C"); }
)
build("CLEANUP");

In general we probably want to pass a parameter to build() indicating whether to run the job.
We may also need a value returned from build() indicating the status of that job.

This may already be possible to some extent with guard..rescue. I need to try some experiments.

Environment: Jenkins 1.492
Build Flow 0.6

Red Hat Enterprise Linux 6.2 64 bit
Sun Java 1.6.0_20
Project: Jenkins
Priority: Major Major
Reporter: Ben Golding
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to