I like that second example! I forget I have the full power of groovy behind
me with the Build Flow
On Thu, Jul 4, 2013 at 2:07 PM, Schalk Cronjé wrote:
> guard/rescue will work, but is not semantically correct. WHen I see a flow
> like that it tells me that jobC is supposed to clean up the mess
guard/rescue will work, but is not semantically correct. WHen I see a flow
like that it tells me that jobC is supposed to clean up the mess caused by
failed job.
Using ignore would be better. Potentially like below
parallel(
{ ignore(UNSTABLE) {
build('jobA')
}
},
{ igno
Use guard/rescue.
guard {
parallel (
{ build("jobA", ...) },
{ build("jobB", ...) },
...
)
} rescue {
build("jobC", ...)
}
That's how I've dealt with it. See "Guard / Rescue" on the Build Flow
Plugin page in the Jenkins wiki:
https://wiki.jenkins-ci.org/display/JENKINS/Bu
I am using the build flow plugin, which I have to say is incredible, so
thanks! I had a question about how I can have something ALWAYS run after a
set of parallel builds. I have something like the following:
parallel (
{ build("jobA", ...) },
{ build("jobB", ...) },
...
)
build("jobC"
