That plugin UI allows only check-patch triggering alas. If you had merged jobs executed
you can just rerun them. If not it is trickier, but if there are any following changes
then they will accumulate everything merged before.
We are restarting jenkins at the moment and this should solve the situation.
On 8 Jan 2019, at 10:18, Yedidyah Bar David <didi(a)redhat.com>
On Tue, Jan 8, 2019 at 10:26 AM Anton Marchukov <amarchuk(a)redhat.com> wrote:
> Hello All.
> We noted that jenkins CI jobs are not always triggered for gerrit changes. While we
are investigating this, I want to remind that you always can trigger / re-trigger
check-patch jobs yourself. Just go to to the link , insert your change id and trigger
>  https://jenkins.ovirt.org/gerrit_manual_trigger/
Can this trigger also build-artifacts?
Used it successfully to trigger check-patch for , but if I select
and press "Trigger selected" after merging, it still triggers
> Anton Marchukov
> Team Lead - Release Management - RHV DevOps - Red Hat
> Devel mailing list -- devel(a)ovirt.org
> To unsubscribe send an email to devel-leave(a)ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
Team Lead - Release Management - RHV DevOps - Red Hat