[Gluster-Maintainers] IMPORTANT: New jenkins triggering method

Raghavendra Talur rtalur at redhat.com
Tue Jan 12 13:51:37 UTC 2016

We have now changed the gerrit-jenkins workflow as follows:

1. Developer works on a new feature/bug fix and tests it locally(run
run-tests.sh completely).
2. Developer sends the patch to gerrit using rfc.sh.

+++Note that no regression runs have started automatically for this patch
at this point.+++

3. Developer marks the patch as +1 verified on gerrit as a promise of
having tested the patch completely. For cases where patches don't have a +1
verified from the developer, maintainer has the following options
a. just do the code-review and award a +2 code review.
b. pull the patch locally and test completely and award a +1 verified.
Both the above actions would result in triggering of regression runs for
the patch.

4. Once the regression runs complete, verification verdict is passed onto
gerrit by jenkins
and maintainer can proceed with the merge using submit button.

Raghavendra Talur
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/maintainers/attachments/20160112/10f4eac0/attachment.html>

More information about the maintainers mailing list