Great news Anton, this will really make stable branch maintainers' life easier!Just out of curiosity since it's just stopped working at some point a few months ago, what was the problem there?On Thu, May 17, 2018 at 12:36 PM, Anton Marchukov <amarchuk@redhat.com> wrote:______________________________Hello All.We have fixed the Rerun-Hooks comment functionality on gerrit.ovirt.org and you should be able to start using it now.The most common use case for this is to rerun all patchset-created hooks on a patch. Just leave a comment with:Rerun-Hooks: alland shortly you will get the hooks to be re-executed and output delivered as a gerrit comment (same as you would just submitted the patch).This also supports rerunning individual hooks. But it is a bit less straightforward as you need to know the hook file name. E.g. the following is possible:Rerun-Hooks: patchset-created.bz.1.check_bug_url, patchset-created.bz.2.check_pr oduct you can see the default hooks list at [1].I think most of the time "Rerun-Hooks: all" will do the job and it is all you need to remember.Note that currently it is possible to rerun online patchset-created hooks.Anton.[1] https://gerrit.ovirt.org/gitweb?p=gerrit-admin.git;a=tree;f= hooks/default-hooks/all --Anton Marchukov
Team Lead - Release Management - RHV DevOps - Red Hat_________________
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-leave@ovirt.org