[Gluster-Maintainers] Some tips on quicker 'smoke' runs

[Amar Tumballi]

Hi maintainers,

Specially, those of you, who normally run 'recheck smoke' for failures in
smoke. I am not sure if you know with one more click on only failed job,
you can goto exact test which failed, and only 'Retrigger' that particular
test to get +1 on smoke (if that passes). It saves a lot of time (and CPU
too), as there are overall 9 tests in smoke, and for a minor one failing,
no need to run everything again.

Can be handy during some known failures which would need a refresh only
after something changes, like SpecApproved/DocApproved. Run only failed
comment-on-issues after the labels are given.

Well, if you have 9-10 mins to wait for every 'smoke' you recheck, then
this email is not for you :-)

Note that the retrigger option is shown on the jenkins web dashboard only
if you login, and it happens automatically through your github login.

Regards,
Amar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/maintainers/attachments/20180505/16ee803d/attachment.html>