Hi all, Is there some way to trigger another check when Jenkins fails because of issues unrelated to the change? For example last time I submitted https://review.openstack.org/14374 Jenkins failed job gate-nova-docs, but that was because some package could not be downloaded properly: 01:31:58 Downloading/unpacking httplib2 (from -r /home/jenkins/workspace/gate-nova-docs/tools/pip-requires (line 20)) 01:31:58 Hash of the package http://pypi.openstack.org/httplib2/httplib2-0.7.6.tar.gz#md5=3f440fff00e0d2d 3c2971693de283cdf (from http://pypi.openstack.org/httplib2/) (<md5 HASH object @ 0x1ac73a0>) doesn't match the expected hash 3f440fff00e0d2d3c2971693de283cdf! 01:31:58 Bad md5 hash for package http://pypi.openstack.org/httplib2/httplib2-0.7.6.tar.gz#md5=3f440fff00e0d2d 3c2971693de283cdf (from http://pypi.openstack.org/httplib2/) It seems I could not do anything about it apart from waiting for another change to be merged and triggering "Rebase change". It's the second time I run into an issue like that. I know some projects workaround it by running checks again after a specific comment containing one word (recheck, rekick, ...). Is there any similar system working / planned for Openstack? Regards, Stanisław Pitucha Cloud Services Hewlett Packard -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6216 bytes Desc: not available URL: <http://lists.openstack.org/pipermail/openstack/attachments/20121015/f7dce85c/attachment.bin>