Open Stack

On Mon, Dec 18, 2017 at 11:29 PM, <Arkady.Kanevsky at dell.com> wrote:

> Thanks for response.
> My recommendation is:
> 1. only allow patches into openstack/ironic-tempest-plugin
> 2. Give Ironic CI owners time period (3 weeks?) to switch their setup to
> only use openstack/ironic-tempest-plugin and not master and report back
> to Ironic CI team if it works for them. If yes, go ahead and switch if not,
> report back.
> 3. At the end of that time, if majority of Ironic CI site complete their
> transition to ironic-tempest-plugin we switch.
>
> Thanks,
> Arkady
>
>
I think this is reasonable. I cringe at knowingly doing something that will
most likely break the third party CI when people are away and cannot
address it. Also, apart from the danger that the third party CIs are
running old versions of the tempest plugins (I doubt that we'll be doing
major overhaul of that in the next 2+ weeks), the reason we have 3rd party
CI is to make sure patches work against those HW. Having most or all of
them being unavailable due to this breakage means that there won't be any
feedback that someone's code would have broken 3rd party CI outside of the
tempest changes.

John, don't you have a patch that removes the tempest plugin from master?
Do most/all of the 3rd party CIs fail due to that? (Or is it not as simple
as that?) Ah, yes, https://review.openstack.org/#/c/527733/ shows that all
the 3rd party CI fail (although I don't know if it is due to that patch or
if they were already failing prior to that).

--ruby
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20171219/90e971dd/attachment.html>