[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [OSSTEST PATCH v13 21/24] Create a flight to test OpenStack with xen-unstable and libvirt
Anthony PERARD writes ("Re: [OSSTEST PATCH v13 21/24] Create a flight to test OpenStack with xen-unstable and libvirt"): > On Tue, Jul 25, 2017 at 07:09:06PM +0100, Ian Jackson wrote: > > Anthony PERARD writes ("[OSSTEST PATCH v13 21/24] Create a flight to test > > OpenStack with xen-unstable and libvirt"): > > > This patch creates a flight "openstack*", with those jobs: > > > > Do you mean it creates a "branch" ? But I don't think it does. I > > predict no changes to the output of mg-list-all-branches. You > > probably want to edit cr-for-branches. > > Maybe branch is the right word, but this patch does not change anything > anymore. I've try to split changes in "make-fligh" from the on in ap-* > and cr-*, but the description is just not clear enough. Maybe Subject: Create devstack jobs (on openstack branches only) blah blah blah The new jobs appear only in the branches openstack-*, which will be introduced in the next patch. So, for now, no overall functional change. ? > Last time I've check, by testing this patch with the next one, those > jobs where only part of a branch names "openstack-ocata" and did not > change anything else. Oh, good. You might mention having done this check, in the commit message. That would save me from being confused, at least. Ian. _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx https://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |