On 4 March 2014 17:07, Jay Pipes <jaypi...@gmail.com> wrote: > I would advise dropping the custom CI setup and going with a method that > specifically uses the upstream openstack-dev/devstack and > openstack-infra/devstack-gate projects. >
This sounds great to me. Thank you for all the work you are doing on simplifying the baseline CI setup. The ideal situation from my perspective would be to use a standard upstream script to create a working CI that can make real tempest runs and vote with my account based on the results (to the sandbox initially). Then I'd branch this script to do the setup that's specific for my driver and to selectively disable tests that are not relevant (if needed). Then once it's looking good the votes could move from the sandbox to the mainline. In future cycles when the CI requirements change I would pull the new upstream scripts and rebase my branch onto them. This could perhaps run in parallel into the sandbox before taking over the mainline work. This seems to be the direction that you are taking things and that sounds wonderful to me.
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
