Re: [Xen-devel] [OSSTEST PATCH v11 20/20] Introduce flight for stable branches of OpenStack

[Ian Jackson <ian.jackson@xxxxxxxxxxxxx>]

Anthony PERARD writes ("Re: [OSSTEST PATCH v11 20/20] Introduce flight for 
stable branches of OpenStack"):
> We decided to track only nova.git, and let osstest clone other trees and
> checkout the HEAD (by having REVISION_* empty). That is fine if we track
> "master" of nova.git.

Right.

> The issue now is if we want to track a branch of OpenStack, like
> "stable/ocata" (which is the latest release), we need to have all trees
> (nova.git, devstack.git, ...) checkout the same branch. (tempest.git
> does not have release specific branch.)

Ah.

> I think this patch is confusing because I originally try to use osstest
> scripts to find which commit to use for every trees and so have add the
> necessary into ./ap-fetch-version. But I could not make that works
> without duplicating some functions and so went with writing
> 'origin/stable/ocata' into REVISION_*.

OIC.

I think it is fine to write origin/stable/ocata into REVISION_*, in
this case.  Of course it means that the sub-trees are not revision
controlled by the osstest push-gate.  IIRC you said that bugs due to
those sub-trees would not be very likely.

> In term of osstest branches, in cr-for-branches, I would like only one
> branch. 'openstack-nova-ocata' would be a the branch that test the
> OpenStack release named 'Ocata'. Later, once this branch run smoothly,
> we can add a branch to test 'master', the development branch of
> OpenStack, it was called 'openstack-nova' in the original 3 patch of
> this patch series.

Aha.

I will go and read the patch again.

Ian.

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