[libvirt] [jenkins-ci PATCH] jenkins: only send one email on build failure

Erik Skultety eskultet at redhat.com
Thu Mar 28 15:59:40 UTC 2019


On Thu, Mar 28, 2019 at 04:51:55PM +0100, Erik Skultety wrote:
> On Thu, Mar 28, 2019 at 10:29:53AM +0000, Daniel P. Berrangé wrote:
> > On Thu, Mar 14, 2019 at 05:25:13PM +0000, Daniel P. Berrangé wrote:
> > > The current config causes jenkins to send a build on every single
> > > failure. This is way too noisy so change it to only send emails on
> > > the transition from good to bad.
> > >
> > > Signed-off-by: Daniel P. Berrangé <berrange at redhat.com>
> > > ---
> > >  jenkins/jobs/autotools.yaml        | 8 ++++----
> > >  jenkins/jobs/generic.yaml          | 8 ++++----
> > >  jenkins/jobs/go.yaml               | 4 ++--
> > >  jenkins/jobs/perl-modulebuild.yaml | 6 +++---
> > >  jenkins/jobs/python-distutils.yaml | 6 +++---
> > >  5 files changed, 16 insertions(+), 16 deletions(-)
> >
> > So this is pushed, and applied to the jenkins server, but it is still
> > sending emails on every failed build. Guess this setting doesn't
> > really do what it is documented todo :-(
>
> Sigh...I haven't noticed earlier, the problem is terminology
> failed vs unstable, so according to jenkins it works as expected and they don't
> seem to have anything alike for failed builds.
> Honestly reading the wiki on what an unstable build is, I'm still not sure I
> understand it.
>
> Erik

There is a plugin though which might be able to open further options to us, but
I don't know how I'd try it, any suggestions?

https://wiki.jenkins.io/display/JENKINS/Email-ext+plugin

Erik




More information about the libvir-list mailing list