Hopefully, our schedule for Kilo will be flexible enough to allocate a session to discuss CI for Third Party in Neutron. So, I completely agree with Sukhdev that all MLs iteration should get us into a formal conclusion and later into guidelines/process for all CI owners.
Edgar From: Sukhdev Kapur <sukhdevka...@gmail.com<mailto:sukhdevka...@gmail.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Date: Wednesday, September 3, 2014 at 4:34 PM To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [neutron] [third-party] collecting recheck command to re-trigger third party CI Incidentally, I replied to Kurt's email this morning on this subject - below is what I wrote. There are several threads with such information. While it is great to express opinions on the MLs, converting them into decisions/conclusions should be done in a formal fashion. I suggested that this be addressed in a session in Kilo - hosted by Kyle/Edgar. -Sukhdev --------------------------- Hi Kurt, We (Arista) were one of the early adapters of the CI systems. We built our system based upon the Neutron requirements as of late last year/early this year. Our CI has been up and operational since January of this year. This is before (or in parallel to Jay Pipes effort of Zuul based CIs). We have invested a lot of effort in getting this done. In fact, I helped many vendors setting up their Jenkin master/slaves, etc. Additionally, we put an effort in coming up with a patch to support "recheck" matching - as it was not supported in Gerritt Plugin. Please see our wiki [1] which has a link to the Google doc describing the recheck patch. At the time the requirement was to support "recheck no bug/bug#". Our system is built to support this syntax. The current Neutron Third party test systems are described in [2] and if you look at the requirements described in [3], it states that a single recheck should trigger all test systems. Having said that, I understand the rationale of your argument. on this thread, and actually agree with your point. I have seen similar comments on various ML threads. My suggestion is that this should be done in a coordinated manner so that everybody understands the requirements, rather than simply throwing it on the mailing list and assuming it is accepted by everybody. This is what leads to the confusion. Some people will take it as a marching orders, others may miss the thread and completely miss the communication. Kyle Mestry (Neutron PTL) and Edgar Magana (Neutron Core) are proposing a session at Kilo Summit in Paris to cover third party CI systems. I would propose that you please coordinate with them and get your point of view incorporated into this session. I have copied them both on this email so that they can share their wisdom on the subject as well. Thanks for all the good work by you and the infra team - making things easier for us. regards.. -Sukhdev [1] https://wiki.openstack.org/wiki/Arista-third-party-testing [2] https://wiki.openstack.org/wiki/NeutronThirdPartyTesting [3] http://ci.openstack.org/third_party.html [https://ssl.gstatic.com/ui/v1/icons/mail/images/cleardot.gif] On Wed, Sep 3, 2014 at 2:34 PM, Anita Kuno <ante...@anteaya.info<mailto:ante...@anteaya.info>> wrote: On 09/03/2014 02:03 PM, Akihiro Motoki 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@lists.openstack.org<mailto:OpenStack-dev@lists.openstack.org> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > Let's add the infra meeting log where this was discussed as reference material as well. http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-08-19-19.02.log.html timestamp: 19:48:38 Thanks, Anita. _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org<mailto: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
