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

Miklos Vajna <vmiklos -AT- collabora.co.uk>
Fri, 23 Feb 2018 16:22:04 +0100

Hi,

On Fri, Feb 23, 2018 at 04:08:24PM +0100, Stephan Bergmann <sbergman@redhat.com> wrote:

I think this was a decision from Norbert, probably because he was worried
about false negatives. A workaround is to watch your inbox (which gets a
mail, whatever is the outcome), rather than the above URL.


Except, you never get a mail about Jenkins success/failure if it wasn't you
who sent the patch set to Gerrit.


Cloph, do you have a view on this? Could we have Jenkins set Verified-1
on the change if the build fails to have a clear separation between "not
yet verified" and "verified but failed" states, immediately visible from
the dashboard?

Thanks,

Miklos

Attachment: signature.asc
Description: Digital signature

Context

Re: Let failed Jenkins builds set Verified: -1 in Gerrit? · Stephan Bergmann
- Re: Let failed Jenkins builds set Verified: -1 in Gerrit? · Miklos Vajna
  - Re: Let failed Jenkins builds set Verified: -1 in Gerrit? · Kaganski Mike
  - Re: Let failed Jenkins builds set Verified: -1 in Gerrit? · Stephan Bergmann
  - Re: Let failed Jenkins builds set Verified: -1 in Gerrit? · Christian Lohmaier
    - Re: Let failed Jenkins builds set Verified: -1 in Gerrit? · Stephan Bergmann
      - Re: Let failed Jenkins builds set Verified: -1 in Gerrit? · Christian Lohmaier
        
        Re: Let failed Jenkins builds set Verified: -1 in Gerrit? · Stephan Bergmann
        
        Re: Let failed Jenkins builds set Verified: -1 in Gerrit? · Stephan Bergmann
        
        Re: Let failed Jenkins builds set Verified: -1 in Gerrit? · Christian Lohmaier
        Re: Let failed Jenkins builds set Verified: -1 in Gerrit? · Stephan Bergmann
        Re: Let failed Jenkins builds set Verified: -1 in Gerrit? · Christian Lohmaier

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.