Let failed Jenkins builds set Verified: -1 in Gerrit?

Stephan Bergmann <sbergman -AT- redhat.com>

Wed, 29 Nov 2017 12:16:24 +0100

Is there any good reason why a failed Gerrit/Jenkins build does not set

the corresponding Gerrit change's Verified flag to -1 (similar to how a

successful such build sets the flag to +1)?

Especially with the poor Jenkins turnaround times, it is hard to tell on

change is not yet ready for submission because Jenkins has not yet built

it or because the Jenkins build failed. The "V" ("Verified") column is

empty in both cases. (And I assume it would contain something like a

red cross if the Verified flag is -1.)

Context

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.