[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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



Anthony PERARD writes ("Re: [OSSTEST PATCH v11 20/20] Introduce flight for 
stable branches of OpenStack"):
> On Fri, Jun 23, 2017 at 06:00:29PM +0100, Ian Jackson wrote:
> > Anthony PERARD writes ("[OSSTEST PATCH v11 20/20] Introduce flight for 
> > stable branches of OpenStack"):
> > So perhaps the branch `openstack-ocata-nova' should be called
> > `openstack-ocata' ?
> 
> Yes, I think that would be enough. You mean "openstack-$version" right?
> (Or with other words "openstack-$release_name".)

Yes.

> > Also, right now I think it's clear that we're not intending to add
> > openstack jobs to existing branches' flights.  But if we were to do
> > that in the future, we would want all the subtrees to be tracked.
> > 
> > Maybe we should have a way for cr-daily-branch to fetch, and push,
> > multiple trees.  We could call ap-fetch-version on every tree,
> > and set the appropriate variable (with determine_version, as you have
> > above).  And then set a variable to call ap-push multiple times, if we
> > get a pass.
> 
> Yes, I first do the work to have the branches been properly setup to
> test openstack of a release, then later I can look into pushing multiple
> branches.

OK.

Ian.

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.