On Wed, Apr 30, 2014 at 5:05 PM, Tim Jackson <[email protected]> wrote:
> I agree that .11 is a huge step backwards for me. As far as I can tell, the
> build flow plugin no longer triggers the failure event of the email-ext
> plugin. So I am no longer getting failure mails for the overall job.
> Setting up a new job to handle the failure mail is redundant and can fail
> itself, thus changing the results. I am more apt to just dump the build
> flow plugin and find a more suitable method.
>
> It is very disappointing to have functionality removed. A lot of us have
> based large amounts of work on what it did.
I think the only way to make it do anything is to set up one job that
just polls the SCM and triggers the build-flow job, then pass all your
build parameters around to a final job executed by the flow that uses
the copy artifacts plugin to gather up the results of whatever the
other elements did. Seems like a lot of clutter and a confusing
process to have to start one job but end up with the results in
another.
--
Les Mikesell
[email protected]
--
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/d/optout.
