On Tue, Jan 8, 2019 at 10:26 AM Anton Marchukov <amarchuk@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 [1], insert your change id and trigger it.
Thanks.
Can this trigger also build-artifacts? Used it successfully to trigger check-patch for [1], but if I select and press "Trigger selected" after merging, it still triggers check-patch. [1] https://gerrit.ovirt.org/96688
-- 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 Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/TLGEZXTCWHEKZQ...
-- Didi