+1 It would also be really helpful if the recheck command is shown in the output of the results from each CI so the developer doesn't even have to visit this page. On Wed, Sep 3, 2014 at 11:03 AM, Akihiro Motoki <amotoki at gmail.com> wrote: > Hi Neutron team, > > There are many third party CI in Neutron and we sometimes/usually > want to retrigger third party CI to confirm results. > A comment syntax varies across third party CI, so I think it is useful > to gather "recheck command" in one place. I struggled to know how to > rerun a specific CI. > > I added to "recheck command" column in the list of Neutron plugins and > drivers [1]. > Could you add "recheck command" of your CI in the table? > If it is not available, please add "N/A". > > Note that supporting recheck is one of the requirements of third party > testing. [2] > I understand not all CIs support it due to various reasons, but > collecting it is useful for developers and reviewers. > > A syntax of "recheck command" is under discussion in infra review [3]. > I believe the column of "recheck command" is still useful even after > the official syntax is defined because it is not an easy thing to know > each CI system name. > > [1] > https://wiki.openstack.org/wiki/Neutron_Plugins_and_Drivers#Existing_Plugin_and_Drivers > [2] http://ci.openstack.org/third_party.html#requirements > [3] https://review.openstack.org/#/c/118623/ > > Thanks, > Akihiro > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Kevin Benton -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140903/91c0c11a/attachment.html>