We are using the Build Flow Plugin (
https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin)
We want to use the guard-rescue structure to do cleanups after jobs fail.
However, we've noticed an annoying behavior: as far as the DSL is
concerned, a build that is "ABORTED" is not failed, so it won't cause the
guard-rescue to be invoked. I can sort of see why it was designed this way,
but unfortunately, the build flow job itself will become failed if there
was an aborted job.
To summarize, in this flow:
guard {
build("job that gets aborted");
} rescue {
build("cleanup job");
}
The cleanup job does not get run, but the build flow job itself gets marked
as a failure.
Additionally, I've found that there is no way to override the build status
set by the build flow. For example, if I use the post-build groovy plugin
to always set the status to SUCCESS, it has no effect; the job's status is
solely dependent on the DSL's resolution.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
