On Wed, Jul 3, 2013 at 9:30 AM, Day, Phil <philip....@hp.com> wrote: > Hi Folks, I can't really speak to the stuff that was here so snip. > > i) Make the default wait time much shorter so that Jenkins runs OK > (tries this with 10 seconds and it works fine), and assume that users will > configure it to a more realistic value. > I know Robert Collins and others would like to see our defaults be reasonable for a mid sized deployment so we shouldn't use a default to accomodate Jenkins. > ii) Keep the default at 120 seconds, but make the Jenkins jobs use a > specific configuration setting (is this possible, and iof so can someone > point me at where to make the change) ? > It is possible. You can expose and set config options through the devstack-gate project [1] which runs the devstack tests in Jenkins. > iii) Increase the time allowed for Jenkins > I don't think we want to do this as it already takes quite a bit of time to get through the gate (the three hour timeout seems long, but sdague and others would have a better idea of what it should be). > iv) The ever popular something else … > Nothing comes to mind immediately.
[1] https://github.com/openstack-infra/devstack-gate You will probably find the devstack-vm-gate.sh and devstack-vm-gate-wrap.sh scripts to be most useful. Clark _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev