<div dir="ltr"><div class="gmail_default" style="font-family:courier new,monospace"><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jun 27, 2014 at 6:35 AM, Daniel P. Berrange <span dir="ltr"><<a href="mailto:berrange@redhat.com" target="_blank">berrange@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On Fri, Jun 27, 2014 at 07:40:51AM -0400, Sean Dague wrote:<br>
> It's clear that lots of projects want 3rd Party CI information on<br>
> patches. But it's also clear that 6 months into this experiment with a<br>
> lot of 3rd Party CI systems, the Gerrit UI is really not great for this.<br>
<br>
</div>That's an understatement about the UI :-)<br>
<div class=""><br>
> It seems what we actually want is a dashboard of these results. We want<br>
> them available when we go to Gerrit, but we don't want them in Gerrit<br>
> itself.<br></div></blockquote><div><br></div><div class="gmail_default" style="font-family:'courier new',monospace">Yes please, and no I'm not signing up for it either :)</div><div class="gmail_default" style="font-family:'courier new',monospace">
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">
><br>
> What if 3rd Party CI didn't vote in Gerrit? What if it instead published<br>
> to some 3rd party test reporting site (a thing that doesn't yet exist).<br>
> Gerrit has the facility so that we could inject the dashboard content<br>
> for this in Gerrit in a little table somewhere, but the data would<br>
> fundamentally live outside of Gerrit. It would also mean that all the<br>
> aggregate reporting of 3rd Party CI that's being done in custom gerrit<br>
> scripts, could be integrated directly into such a thing.<br>
<br>
</div>Agreed, it would be a great improvement in usability if we stopped all<br>
CI systems, including our default Jenkins, from ever commenting on<br>
reviews. At most gating CIs should +1/-1. Having a table of results<br>
displayed, pulling the data from an external result tracking system<br>
would be a great idea.<br>
<br>
Even better if this external system had a nice button you can press<br>
to trigger re-check, so we can stop using comments for that too.<br>
<br>
To me the ideal world is where the only things adding comments to<br>
reviews are human and their comments are actually about the code<br>
in the patch :-)<br>
<br>
Regards,<br>
Daniel<br>
<span class="HOEnZb"><font color="#888888">--<br>
|: <a href="http://berrange.com" target="_blank">http://berrange.com</a> -o- <a href="http://www.flickr.com/photos/dberrange/" target="_blank">http://www.flickr.com/photos/dberrange/</a> :|<br>
|: <a href="http://libvirt.org" target="_blank">http://libvirt.org</a> -o- <a href="http://virt-manager.org" target="_blank">http://virt-manager.org</a> :|<br>
|: <a href="http://autobuild.org" target="_blank">http://autobuild.org</a> -o- <a href="http://search.cpan.org/~danberr/" target="_blank">http://search.cpan.org/~danberr/</a> :|<br>
|: <a href="http://entangle-photo.org" target="_blank">http://entangle-photo.org</a> -o- <a href="http://live.gnome.org/gtk-vnc" target="_blank">http://live.gnome.org/gtk-vnc</a> :|<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</font></span></blockquote></div><br></div></div>