Neither the stable-compat job group nor the templates they define
are used any longer, so remove them any any instantiations thereof.
Also remove a stray voting override for one of these jobs left
behind in the zuul layout.
Change-Id: Ia40d8cbf8cef803617509aeca20a9f1ec79d0880
The library testing jobs aren't really about testing the libraries,
they are about sniff testing them in a live deploy. By only using the
neutron jobs we are effectively testing the entirety of the integrated
release, minus a *very* small amount of code in nova.
This will reduce the amount of random fail on these jobs, use a lot
less nodes, and achieve effectively the same results. Any n-net only
breaks that slip through should be addressed by other mechanisms,
because the likelyhood that n-net is so dramatically using libraries
differently from the rest of nova is vanishlying small.
Change-Id: I1dcd8558b98443ffa9a3a01c2e877bd64bb96296
We are making devstack use client libraries from pypi instead of from
git. Before we do that we need to change the client library job
definitions to support testing themselves against changes in their own
git trees. This is equivalent to what was done with the oslo libraries.
This adds the lib-forward-testing to the client libraries for testing,
and purges the integrated gate jobs from them. It also changes the
stable-compat jobs to be driving by -src-{name} jobs, which will test
a client library with openstack servers from git, all the rest of the
client libraries from pypi, and the {name} library from git. So a
python-novaclient change will be tested with nova stable/*, released
glance/cinder clients, but the new zuul ref for python-novaclient.
Co-Authored-By: Joshua Hesketh <josh@nitrotech.org>
Needed-By: I26fac0ccf8fd4818e24618d56bf04b32306f88f6
Change-Id: I81b0d228e7769758c61e5b0323ecfce8c8886d39