Doug Wiegley <do...@a10networks.com> wrote on 09/03/2014 11:24:24 PM:
> From:
>
> Doug Wiegley <do...@a10networks.com>
> Date:
>
> 09/03/2014 11:25 PM
>
> Subject:
>
> Re: [openstack-dev] [neutron] [third-party] collecting recheck
> command to re-trigger third party CI
>
> Hi all,
>
> May I suggest putting your feedback into this review, which is on the
same
> subject?
>
> https://review.openstack.org/#/c/118623/
Thanks Doug, I just saw this thread - yes this patch was the result of
infra
IRC channel and Third Party meeting discussions. I believe the proper way
to
specify if individual CI system recheck is supported is to have this shown
in
CI system's wiki page, which is also now a requirement. If the CI system
does
not support an individual recheck, then the default behavior would be to
just
support "recheck" as is currently required.
Any feedback on this proposal is welcomed in the patchset noted above.
Kurt Taylor (krtaylor)
>
>
> Thanks,
> doug
>
> On 9/3/14, 8:57 PM, "trinath.soman...@freescale.com"
> <trinath.soman...@freescale.com> wrote:
>
> >This is a Good option to go with.
> >
> >To trigger a specific CI, CI can have their own string or in a community
> >specified format. Like retrigger-freescale ..
> >
> >Also, in the ML or in IRC rooms, I have seen many people asking on how
to
> >recheck with an X CI.
> >
> >And many people are not aware of what string to use to trigger a recheck
> >for certain CI.
> >
> >As we have now a separate page for each CI, it would be good to have
> >"Trigger String" too in those pages.
> >
> >+1 to Akihiro Motoki for this email.
> >
> >
> >
> >--
> >Trinath Somanchi - B39208
> >trinath.soman...@freescale.com | extn: 4048
> >
> >-----Original Message-----
> >From: Akihiro Motoki [mailto:amot...@gmail.com]
> >Sent: Wednesday, September 03, 2014 11:34 PM
> >To: OpenStack Development Mailing List
> >Subject: [openstack-dev] [neutron] [third-party] collecting recheck
> >command to re-trigger third party CI
> >
> >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_Plugi
> >n_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@lists.openstack.org
> >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >_______________________________________________
> >OpenStack-dev mailing list
> >OpenStack-dev@lists.openstack.org
> >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
