[openstack-dev] [Neutron][Third-Party][Infra] Optimize third party resources

Jaume Devesa devvesa at gmail.com
Thu Jun 12 16:20:13 UTC 2014


Hello all,

I've just submitted a patch[1] to solve a bug in Neutron. All the
third-party plugins has voted as +1 but Jenkins has refused the patch
because of the '.' dot at the end of the commit summary line.

I know that is my fault, because I should run the ./run_tests.sh -p after
modify the commit message, but:

since the official Jenkins runs more gates, tests and checks than the rest
of third-party Jenkins, wouldn't be better to run third party jobs after
official Jenkins has verified the patch? I think that would relax the load
on the third party infrastructures and maybe they can be more reactive in
the 'good' patches.


​[1]: https://review.openstack.org/#/c/99679/2​

-- 
Jaume Devesa
Software Engineer at Midokura
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140612/ce86b5e9/attachment.html>


More information about the OpenStack-dev mailing list