Hi, When we send a patch to gerrit.ovirt.org for VDSM project, jenkins start the building job and if everything is nice it set the flag 'verified'. Is it possible to jenkins not set the flag verified? It's looks like more building validation then a real test.

Also, is it possible to Jenkins stop saying that it starts a test and just tell us when something is broken?

Thanks!

----- Original Message ----- > From: "Itamar Heim" <iheim(a)redhat.com&gt; > To: dougsland(a)redhat.com > Cc: infra(a)ovirt.org > Sent: Friday, March 8, 2013 9:43:30 PM > Subject: Re: oVirt Jenkins - setting verified flag / messaging > > On 03/07/2013 08:50 PM, Douglas Landgraf wrote: >> Hi, >> >> When we send a patch to gerrit.ovirt.org for VDSM project, jenkins >> start >> the building job and if everything is nice it set the flag >> 'verified'. >> Is it possible to jenkins not set the flag verified? >> It's looks like more building validation then a real test. > > possible. already done afaik (changed 1 to 0 on gerrit trigger side) > >> >> Also, is it possible to Jenkins stop saying that it starts a test >> and >> just tell us when something is broken? not possible via current plugin. i know someone from the rhevm team is looking into sending a patch to the gerrit trigger jenkins plugin [1] to stop these alerts. (or at least make them configurable) meanwhile, the only solution i can think of is changing ability of the jenkins user to email reviewers, which i think is only supported from gerrit 2.5.2: (we're using 2.4.2) from the plugin doc [2]: "Reduce number of notification emails Since the trigger adds a comment in Gerrit for each build start and end, usually all the reviewers get a notification email. This can get quite annoying. However, it's possible to configure Gerrit so that only the change owner and people who starred the change get a notification email. To do this DENY the 'Email Reviewers' capability for the Gerrit user that is used by Jenkins. See https://gerrit-review.googlesource.com/Documentation/access-control.html#... [1] https://github.com/jenkinsci/gerrit-trigger-plugin [2] https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger > > main problem is then we don't know when it stopped working > altogether... > but doing a single comment for all starting jobs would reduce amount > of > noise dramatically > >> >> Thanks! > > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra >