Re: [Xen-devel] [PATCH OSSTEST v3 3/3] Create a flight to test OpenStack with xen-unstable and libvirt

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

Anthony PERARD writes ("[PATCH OSSTEST v3 3/3] Create a flight to test 
OpenStack with xen-unstable and libvirt"):
> Signed-off-by: Anthony PERARD <anthony.perard@xxxxxxxxxx>
> 
> ---
> Change in V3:
> - Switch to "track" Nova tree instead of devstack.
>     Nova is the service we care about from a Xen point of view.
>     Also it is updated much more often than devstack.
> - Use TREE_OPENSTACK_ as prefix for all trees variables.
> - Change the filter, keep only *-devstack jobs.
> - Add stuff into ./ap-push
> - Add stuff into ./cr-daily-branch.
> - Add 'openstack' into ./cr-for-branches.
...
> +  job_create_test test-$xenarch$kern-$dom0arch-devstack \
> +    test-devstack libvirt $xenarch $dom0arch \
> +    tree_devstack=$TREE_OPENSTACK_DEVSTACK \
> +    tree_requirements=$TREE_OPENSTACK_REQUIREMENTS \
> +    tree_keystone=$TREE_OPENSTACK_KEYSTONE \
> +    tree_glance=$TREE_OPENSTACK_GLANCE \
> +    tree_cinder=$TREE_OPENSTACK_CINDER \
> +    tree_nova=$TREE_OPENSTACK_NOVA \
> +    tree_tempest=$TREE_OPENSTACK_TEMPEST \
> +    revision_devstack=master \
> +    revision_requirements=master \
> +    revision_keystone=master \
> +    revision_glance=master \
> +    revision_cinder=master \
> +    revision_nova=master \
> +    revision_tempest=master \

All these revision_FOO=master are rather odd.  You seem to be creating
a push gate which maintains a tested revision of `openstack-nova'.  Is
that what you want ?  If so, then it's not really clear to me that
what you want to do is to simply pick up new master revisions of these
other git trees.  It might be better to obtain a bunch of revision
ids, test them all together, and push them together ?  (This is not
something that osstest can do right now but it doesn't seem
difficult.)

If you don't want to make a push gate, then you probably want to do
away with the changes to ap-fetch and ap-push.

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel