<html><body>
<p><tt><font size="2">Doug Wiegley <dougw@a10networks.com> wrote on 09/03/2014 11:24:24 PM:<br>
<br>
> From:</font></tt><br>
<tt><font size="2">> <br>
> Doug Wiegley <dougw@a10networks.com></font></tt><br>
<tt><font size="2"><br>
> Date:</font></tt><br>
<tt><font size="2">> <br>
> 09/03/2014 11:25 PM</font></tt><br>
<tt><font size="2">> <br>
> Subject:</font></tt><br>
<tt><font size="2">> <br>
> Re: [openstack-dev] [neutron] [third-party] collecting recheck <br>
> command to re-trigger third party CI</font></tt><br>
<tt><font size="2">> <br>
> Hi all,<br>
> <br>
> May I suggest putting your feedback into this review, which is on the same<br>
> subject?<br>
> <br>
> <a href="https://review.openstack.org/#/c/118623/">https://review.openstack.org/#/c/118623/</a></font></tt><br>
<br>
<tt><font size="2">Thanks Doug, I just saw this thread - yes this patch was the result of infra </font></tt><br>
<tt><font size="2">IRC channel and Third Party meeting discussions. I believe the proper way to </font></tt><br>
<tt><font size="2">specify if individual CI system recheck is supported is to have this shown in</font></tt><br>
<tt><font size="2">CI system's wiki page, which is also now a requirement. If the CI system does</font></tt><br>
<tt><font size="2">not support an individual recheck, then the default behavior would be to just</font></tt><br>
<tt><font size="2">support "recheck" as is currently required.</font></tt><br>
<br>
<tt><font size="2">Any feedback on this proposal is welcomed in the patchset noted above.</font></tt><br>
<font size="2" face="sans-serif"><br>
Kurt Taylor (krtaylor)</font><br>
<tt><font size="2"> <br>
> <br>
> <br>
> Thanks,<br>
> doug<br>
> <br>
> On 9/3/14, 8:57 PM, "trinath.somanchi@freescale.com"<br>
> <trinath.somanchi@freescale.com> wrote:<br>
> <br>
> >This is a Good option to go with.<br>
> ><br>
> >To trigger a specific CI, CI can have their own string or in a community<br>
> >specified format. Like retrigger-freescale ..<br>
> ><br>
> >Also, in the ML or in IRC rooms, I have seen many people asking on how to<br>
> >recheck with an X CI.<br>
> ><br>
> >And many people are not aware of what string to use to trigger a recheck<br>
> >for certain CI.<br>
> ><br>
> >As we have now a separate page for each CI, it would be good to have<br>
> >"Trigger String" too in those pages.<br>
> ><br>
> >+1 to Akihiro Motoki for this email.<br>
> ><br>
> ><br>
> ><br>
> >--<br>
> >Trinath Somanchi - B39208<br>
> >trinath.somanchi@freescale.com | extn: 4048<br>
> ><br>
> >-----Original Message-----<br>
> >From: Akihiro Motoki [<a href="mailto:amotoki@gmail.com">mailto:amotoki@gmail.com</a>]<br>
> >Sent: Wednesday, September 03, 2014 11:34 PM<br>
> >To: OpenStack Development Mailing List<br>
> >Subject: [openstack-dev] [neutron] [third-party] collecting recheck<br>
> >command to re-trigger third party CI<br>
> ><br>
> >Hi Neutron team,<br>
> ><br>
> >There are many third party CI in Neutron and we sometimes/usually want to<br>
> >retrigger third party CI to confirm results.<br>
> >A comment syntax varies across third party CI, so I think it is useful to<br>
> >gather "recheck command" in one place. I struggled to know how to rerun a<br>
> >specific CI.<br>
> ><br>
> >I added to "recheck command" column in the list of Neutron plugins and<br>
> >drivers [1].<br>
> >Could you add "recheck command" of your CI in the table?<br>
> >If it is not available, please add "N/A".<br>
> ><br>
> >Note that supporting recheck is one of the requirements of third party<br>
> >testing. [2] I understand not all CIs support it due to various reasons,<br>
> >but collecting it is useful for developers and reviewers.<br>
> ><br>
> >A syntax of "recheck command" is under discussion in infra review [3].<br>
> >I believe the column of "recheck command" is still useful even after the<br>
> >official syntax is defined because it is not an easy thing to know each<br>
> >CI system name.<br>
> ><br>
> >[1] <br>
> ><a href="https://wiki.openstack.org/wiki/Neutron_Plugins_and_Drivers#Existing_Plugi">https://wiki.openstack.org/wiki/Neutron_Plugins_and_Drivers#Existing_Plugi</a><br>
> >n_and_Drivers<br>
> >[2] <a href="http://ci.openstack.org/third_party.html#requirements">http://ci.openstack.org/third_party.html#requirements</a><br>
> >[3] <a href="https://review.openstack.org/#/c/118623/">https://review.openstack.org/#/c/118623/</a><br>
> ><br>
> >Thanks,<br>
> >Akihiro<br>
> ><br>
> >_______________________________________________<br>
> >OpenStack-dev mailing list<br>
> >OpenStack-dev@lists.openstack.org<br>
> ><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
> ><br>
> >_______________________________________________<br>
> >OpenStack-dev mailing list<br>
> >OpenStack-dev@lists.openstack.org<br>
> ><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
> <br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> OpenStack-dev@lists.openstack.org<br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
> <br>
</font></tt></body></html>