<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 25 March 2015 at 14:21, Sean Dague <span dir="ltr"><<a href="mailto:sean@dague.net" target="_blank">sean@dague.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 03/25/2015 09:03 AM, Gary Kotton wrote:<br>
><br>
> From: Jordan Pittier <<a href="mailto:jordan.pittier@scality.com">jordan.pittier@scality.com</a><br>
> <mailto:<a href="mailto:jordan.pittier@scality.com">jordan.pittier@scality.com</a>>><br>
> Reply-To: OpenStack List <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
> <mailto:<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>>><br>
<span class="">> Date: Wednesday, March 25, 2015 at 1:47 PM<br>
> To: OpenStack List <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
</span>> <mailto:<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>>><br>
<span class="">> Subject: Re: [openstack-dev] [nova] CI report formatting (citrix /<br>
> hyperv / vmware )<br>
><br>
> Hi<br>
> On Wed, Mar 25, 2015 at 12:39 PM, Sean Dague <<a href="mailto:sean@dague.net">sean@dague.net</a><br>
</span><span class="">> <mailto:<a href="mailto:sean@dague.net">sean@dague.net</a>>> wrote:<br>
><br>
> Currently Citrix, HyperV, and VMWare CI systems reporting on Nova<br>
> patches have a different formatting than the standard that Jenkins and<br>
> other systems are using:<br>
><br>
> * test-name-no-spaces <a href="http://link.to/result" target="_blank">http://link.to/result</a><br>
</span>> <<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__link.to_result&d=AwMFaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=VlZxHpZBmzzkWT5jqz9JYBk8YTeq9N3-diTlNj4GyNc&m=EtHYlIXfK33bYsGf2k8XbFtgWlkcm_VdZCrFHTLEdiE&s=5SS-txUrD3o8KS3QIaCL3XMBbeCYK5CjmzmuxDda7Oc&e=" target="_blank">https://urldefense.proofpoint.com/v2/url?u=http-3A__link.to_result&d=AwMFaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=VlZxHpZBmzzkWT5jqz9JYBk8YTeq9N3-diTlNj4GyNc&m=EtHYlIXfK33bYsGf2k8XbFtgWlkcm_VdZCrFHTLEdiE&s=5SS-txUrD3o8KS3QIaCL3XMBbeCYK5CjmzmuxDda7Oc&e=</a>><br>
<span class="">> : [SUCCESS|FAILURE] some<br>
> comment about the test<br>
><br>
> I don't want to talk for Citrix, HyperV or VMWare but the "standard"<br>
> only work if you use Zuul in your CI. I am using a setup based on a<br>
> Jenkins plugin called gerrit-trigger and there's no way to format the<br>
> message the way it's expected...<br></span></blockquote><div><br></div><div>FWIW I help maintain one the VMware CIs (the one voting on neutron and network-related patches for devstack and tempest).</div><div>We use gerrit-trigger too (mostly out of lazyness, no other real reason), but we're able to format the message posted back to gerrit.</div><div>For posting back votes we use the "gerrit review" command to post the message in the standard format.<br></div><div><br></div><div>I think the same process is adopted also by the CI voting on nova. However, the job result string is not being posted. I will double check with the respective owners.</div><div><br></div><div>Salvatore</div><div> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
><br>
><br>
> This means these systems don't show up in the CI rollup block -<br>
> <a href="http://dl.dropbox.com/u/6514884/screenshot_158.png" target="_blank">http://dl.dropbox.com/u/6514884/screenshot_158.png</a><br>
</span>> <<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__dl.dropbox.com_u_6514884_screenshot-5F158.png&d=AwMFaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=VlZxHpZBmzzkWT5jqz9JYBk8YTeq9N3-diTlNj4GyNc&m=EtHYlIXfK33bYsGf2k8XbFtgWlkcm_VdZCrFHTLEdiE&s=nIjYwznh1_8aVBSz-XVEJrpNaMsDfqyekOQ2IhiHTo8&e=" target="_blank">https://urldefense.proofpoint.com/v2/url?u=http-3A__dl.dropbox.com_u_6514884_screenshot-5F158.png&d=AwMFaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=VlZxHpZBmzzkWT5jqz9JYBk8YTeq9N3-diTlNj4GyNc&m=EtHYlIXfK33bYsGf2k8XbFtgWlkcm_VdZCrFHTLEdiE&s=nIjYwznh1_8aVBSz-XVEJrpNaMsDfqyekOQ2IhiHTo8&e=</a>><br>
<span class="">><br>
><br>
> Current the Vmware CI will vote +1 iff the patch has passed on the CI.<br>
> We can investigate adding this to the CI rollup block.<br>
><br>
><br>
><br>
> I'd really like that to change. The CI rollup block has been extremely<br>
> useful in getting the test results of a patch above the fold, and the<br>
> ability to dig into them clearly. I feel like if any CI system isn't<br>
> reporting in standard format that's parsible by that, we should probably<br>
> turn it off.<br>
><br>
><br>
> I do not think that we should turn this off. They have value. It would<br>
> be nice if things were all of the same format, which I guess that this<br>
> is the intension of the mail. Lets all try and make an effort to work<br>
> towards this goal.<br>
<br>
</span>Right, honestly, I don't want these turned off, I want them reporting in<br>
a more standard format. But I do think if they don't report in a<br>
standard format it will cause problems and add to them being ignored.<br>
<div class="HOEnZb"><div class="h5"><br>
-Sean<br>
<br>
--<br>
Sean Dague<br>
<a href="http://dague.net" target="_blank">http://dague.net</a><br>
<br>
</div></div><br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</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>
<br></blockquote></div><br></div></div>