[openstack-dev] [neutron][third-party] Protocol for bringing up CI for a new driver?

Salvatore Orlando sorlando at nicira.com
Tue Aug 5 08:34:24 UTC 2014

Hi Luke,

Once in place, the CI system should be able to pick up the patches from the
new plugin or driver on gerrit.
In my opinion, successful CI runs against those patches should constitute a
sufficient proof of the validity of the CI system.

Il 05/ago/2014 09:57 "Luke Gorrie" <luke at snabb.co> ha scritto:

> Howdy,
> Could somebody please clarify the protocol for bringing up a CI for a new
> Neutron driver?
> Specifically, how does one resolve the chicken-and-egg situation of:
> 1. CI should be enabled before the driver is merged.
> 2. CI should test the refspecs given by Gerrit, which will not include the
> code for the new driver itself until after it has been merged.
> So what is the common practice for using the new driver in tests during
> the time window prior to its merge?
> Cheers!
> -Luke
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140805/ebe451e7/attachment.html>

More information about the OpenStack-dev mailing list