[Gluster-infra] [Gluster-devel] Reconfigured Jenkins (smoke) jobs to not overwrite/reset regression-test results

Atin Mukherjee atin.mukherjee83 at gmail.com
Sat May 30 11:35:57 UTC 2015

On 30 May 2015 16:49, "Niels de Vos" <ndevos at redhat.com> wrote:
> Hi all,
> many of the Jenkins regression-tests have finished before all the smoke
> jobs were done (we have fewer NetBSD slaves and the smoke tests were
> waiting long in the queue). This caused the Verified +1 from the
> regression-tests to be overwritten with Verified=0 once the smoke
> results were available.
> The configuration change I have made in the several Jenkins jobs that
> are doing smoke testing, is like this:
>   - open a Jenkins job configuration
>   - scroll down to "Gerrit trigger"
>   - click the [Advanced...] button
>   - scroll down to "Gerrit Reporting Values"
>   - enable "Skip Vote" for "Successful"
>   - click the [Save] button on the bottom of the page
> This means that any successful result (Verified=0) will not get passed
> on to Gerrit. If the regression test finished before, it will not be
> overwritten anymore. This not-overwriting will be marked in a comment in
> Gerrit with "SUCCESS (skipped)" next to the job. If a smoke test fails,
> the failure will be reported and Verified=-1 gets set.
> Well, that is the/my theory at least. Let me know if you notice any
I would suggest to have 3 acks, a separate vote id for smoke as well.
> issues.
> Thanks,
> Niels
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-infra/attachments/20150530/f10fccd0/attachment.html>

More information about the Gluster-infra mailing list