These jobs are not used in zuul/layout.yaml but defined, remove them:
gate-neutron-vpnaas-dsvm-functional-ubuntu-xenial
gate-oslo.messaging-src-dsvm-full-zmq-default-ubuntu-xenial
gate-tempest-dsvm-networking-odl-carbon-snapshot-v2driver-nv
gate-tempest-dsvm-neutron-src-oslo.versionedobjects-ubuntu-xenial-newton
gate-tempest-dsvm-neutron-src-oslo.versionedobjects-ubuntu-xenial-ocata
periodic-tempest-dsvm-neutron-identity-v3-only-full-ubuntu-xenial-master
Remove now unused stable-compat-jobs template and job-group.
Remove now unused
'{pipeline}-tempest-dsvm-neutron-identity-v3-only-full-{node}{suffix}'
job-template.
Change-Id: I572c8700ba1300b8f01d83d33ba6b2993104680e
* https://review.openstack.org/#/c/474164/ addes
tox -e plugin-sanity-check to perform the same.
* It also replaces the old job tempest plugin sanity job.
Change-Id: I86a534043d2c0ba2d26ef14b75ac06659a017f2d
All jobs have been removed already, adjust job-group to not define
unused jobs. With mitaka EOL we do not need to forward test on mitaka
anymore.
Change-Id: I2226909bfe8ba13e5f7be2f1328c66602c2b88c0
While calling python script for getting tempest plugin list,
the tempest-plugin-sanity job got failed due to missing requests
python package. So, in order to overcome this failure, we can
switch to shell script
Change-Id: I472e68c495b7ae00654b2f2b5951c43835af1427
Convert some more job templates to use local_conf.
This handles files [s-z]* and converts all templates where a conversion
was directly possible.
Change-Id: Idf3143ea38709d69e8de01667bc129fe9cacdbca
Some of the projects having tempest-plugin like aodh does not
have test-requirements.txt file which leds to the failure of
tempest-plugin-sanity job while installing test packages from
it. In order to avoid the failure we need to check for that
file then install.
Change-Id: I09f2ab6d2187f159f7ddb0068111ac276ca7bbcf
Currently the requirements of in-tree tempest plugins are
kept in test-requirements.txt of each project. On doing
pip install <project>, will just install all the packages
required for that project and on listing tempest plugin
tests in a tempest workspace will give dependency error
and tempest-plugin-sanity job will fails. In order to avoid
the above failure we need to do the same.
Change-Id: I84a6c4feb11e28e98edf86e59ff0813eba856426
* since on using zuul-git-prep, openstack/tempest is
the current $workspace and earlier we were using the
wrong path which leds to failure of excution of above
script and further steps using that path. Fixing the
workspace path fixes the issue.
Change-Id: I9f5b3190adfb60a639b10cbbf706369b2d18c48c
* It will clone tempest and get a project list having tempest plugin
* Create virtualenv and installs tempest and other project plugins
* Create tempest workspace
* List tempest plugins
* List tests
* It will help to find tempest plugins issues and dependency mismatch.
Change-Id: Idf04917b0fe8ad4b73d24d8874613d6911897f02
With I0edf1d88c136c3b910a5773690a603eeacb50266 we want to disable running
Cinder V1 Tempest tests. So let's add a job in the experimental queue
to still run these tests, on demand.
Change-Id: I29db63b96327c2e00ea07dd28730739f2e437448
We have now some rather long job-template names, shorten them with
replacing job-suffix with suffix.
Before this change we had 1500 usages of job-suffix and 700 of just
suffix. This change therefore unifies to one setting.
Note that this does not change any job names at all, they are unchanged,
it changes and shortens only the names of job-templates.
Change-Id: I514df039a848d9f6619bca3adc05dfb84a761fc9
Switch master and newton jobs to run on xenial, older branches test on
trusty.
Note that we have
{pipeline}-tempest-dsvm-neutron-src-{name}-{node}{job-suffix}' as a
clone of {pipeline}-tempest-dsvm-neutron-src-{name}-{job-suffix}', we
can merge these now.
This changes also the python-troveclient specific job since it uses
lib-forward-testing in zuul.
Use lib-forward-testing template in zuul when possible.
Change-Id: Icd4454d02c89c9912a0952b073b62d515300165a
We recently introduced a new Newton stable compat job [1] for projects
such as the oslo libraries.
As things are now, it is currently voting in stable/mitaka branch
reviews and it is probably not expected for Newton jobs to be passing
on Mitaka backports. Example of such failing backport here [2].
This change is analogous to the adjustments we did when Mitaka
released [3].
[1]: https://review.openstack.org/#/c/375111/
[2]: https://review.openstack.org/#/c/389190/
[3]: https://review.openstack.org/#/c/295500/
Change-Id: I04112e13ca69998c069c9e30f55e1f069f902253
Once every project has a mitaka branch move the stable compat jobs up
from liberty to mitaka. Note do not merge this until every project has a
mitaka branch otherwise we will be testing against master which provides
no stable compat information.
Change-Id: I30ac575fd4f58f4c37950388b707c133bd4bf9ca
In zuul/layout.yaml we only use
gate-tempest-dsvm-test-accounts-src-tempest-lib, no need to define
this job for an extra 45 repositories. Remove it from
lib-forward-testing and move it to tempest-lib.
Change-Id: Idc2da1037fc2b67e77838f826b020d8edff6e8e3
Between the Icehouse and Juno releases, OpenStack changed its
supported Ubuntu LTS platform from Precise to Trusty. In support of
continuing testing stable/icehouse and prior branches on Precise
while starting to test newer branches on Trusty, a branch-based
decision tree was introduced into our Zuul configuration by way of
complex parameter functions with an ever growing list of regular
expression matches on job names.
Now that Icehouse is EOL (in fact, Juno is too) this simply adds
unnecessary complexity and an attractive nuisance for cargo-cult
copying into new job and job-template definitions which don't even
need it. In preparation to remove the associated parameter
functions, get rid of multiple labels in all jobs and set them to
whatever label Zuul would ultimately select.
This change touches a vast number, possibly a majority, of our jobs
and so manual jenkins-jobs updates on all Jenkins masters will be
needed after this merges, before it's safe to approve the
corresponding Zuul configuration cleanup.
Change-Id: Ic952ee02da2c77fe2ace81c4e2fa87531be6119c
To debug lp1524717 - and other bugs in future related to the
pre-provisioned test accounts code branch, I need the abililty
to add debug statement on tempest-lib, while using the
preprovisioned test accounts setup.
This new experimental job allows doing exactly that by:
- create a debugging patch in tempest-lib
- pickup that patch via depends-on in a tempest patch
- check experimental on the tempest patch
Change-Id: I0feda498016686499493856b86a73f132613dd41
During the Tokyo summit discussions, there were concerns raised
about backward compatability guarantees with oslo libraries. The
main reason was that in liberty global-requirements we do not
cap the versions for oslo libraries and any oslo release in
support of mitaka is likely to break the stable/liberty branch.
We need to add additional jobs to make sure a change in oslo
library in master does not break liberty.
We had this support earlier which was removed in change id:
Ia40d8cbf8cef803617509aeca20a9f1ec79d0880
We cannot just revert that change since a lot of changes have
happened since April. We should run this new job against master
as a check job and also should not vote until next summit.
Change-Id: Idcbb3e8c71b0be97c7ab78c426ac363388f46633
As clarkb suggested on #openstack-infra at 17:46 2015-10-22:
"maybe we should s/branch-designator/job-suffix/g in all those files
as job-suffix makes more sense considering how branch-designator has been
used".
The rename should make it easier for newcomers to understand
these jobs.
This renames branch-designator everywhere in jenkins/jobs/*.
Change-Id: Icb11271b958d92957fb9907ff03c0b898d7b76fc
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
Monty Taylor