Open Stack

On 06/12/2014 12:20 PM, Jaume Devesa wrote:
> 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​
> 
> 
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
Well then we are in a situation where development ceases until the third
party systems respond. Which is not a situation we want to put ourselves
in. We actually are actively avoiding that situation.

The failure on the '.' at the end of the commit title is a style test,
not something the third party tests would run anyway.

Thanks,
Anita.