Hope this links helps you http://www.joinfu.com/2014/01/understanding-the-openstack-ci-system/ http://www.joinfu.com/2014/02/setting-up-an-external-openstack-testing-system/ http://www.joinfu.com/2014/02/setting-up-an-openstack-external-testing-system-part-2/ -- Trinath Somanchi - B39208 trinath.somanchi at freescale.com | extn: 4048 From: Luke Gorrie [mailto:luke at tail-f.com] Sent: Tuesday, August 05, 2014 5:02 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron][third-party] Protocol for bringing up CI for a new driver? Hi Salvatore, On 5 August 2014 10:34, Salvatore Orlando <sorlando at nicira.com<mailto:sorlando at nicira.com>> wrote: 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. That sounds good to me. Is there already an easy way to pick up the patches with devstack? (would one create a local repo, do some git-fu to merge the driver, then point devstack's NEUTRON_REPO there?) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140805/0ae09549/attachment.html>