It's not related to any hooks, the jenkins job configuration was set to trigger
on any comment that had the string 'Verified +1' and unfortunately whoever
configured it did not realize that any successful jenkins run adds a comment
that matches, thus creating a loop where jenkins triggers itself each time it
passes the tests for each patch.

On 06/02, Yevgeny Zaspitsky wrote:
> Hi. 
> 
> Look at this patch: https://gerrit.ovirt.org/#/c/40923/ 
> 
> patch set 4 got 4! findbugs job runs 
> patch set 5 got 2 runs up until now but still counting... 
> 
> 
> Regards, 
> Yevgeny Zaspitsky 

> _______________________________________________
> Infra mailing list
> [email protected]
> http://lists.ovirt.org/mailman/listinfo/infra


-- 
David Caro

Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D

Tel.: +420 532 294 605
Email: [email protected]
Web: www.redhat.com
RHT Global #: 82-62605

Attachment: pgpHIno7kY1ha.pgp
Description: PGP signature

_______________________________________________
Infra mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/infra

Reply via email to