Perhaps Jenkins can display a better message to start with. Being new to openstack, i had no clue on what was happening. However, the fix was simple once understood.
The current message made me to think something was wrong with jenkins environment setup. Regards, Amit *CloudByte Inc.* <http://www.cloudbyte.com/> On Fri, Jul 4, 2014 at 5:39 PM, Duncan Thomas <duncan.tho...@gmail.com> wrote: > On 30 June 2014 07:47, Steve Kowalik <ste...@wedontsleep.org> wrote: > > Personally, I think generating and comparing a sample config every build > > is daft, and a sample configuration should be generated during sdist or > > something. > > This argument has gone back and forth several times. > > There is definite value to a reviewer in seeing the sample conf > changes - it is usually the first thing I look for with a change, to > get a feel what what has been done and look for obvious back > compatibility issue, of which there have been lots. > > Gating on it in its current form is clearly broken since it doesn't > take into account the libraries from OSLO might have changed things. > Ideally jenkins would, after installing all the deps, git checkout the > parent, generate the conf, checkout the change, generate the conf and > post up the diffs, but coding that up is tricky. > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
