Rally team finally added native Zuul V3 jobs (with a bunch of separate
roles and etc) and for simplification of maintainance, it would be
nice to use them.
Needed-By: If5d17fe2b1965ceed578fe20168d011c4f087242
Needed-By: I5cc99b67495e2e10264f1cb89b25b37f5f7af66b
Change-Id: Idc780fd3095e2d5e0e170fba7ce15580c73048be
Local test run definitions were added for running with Python
3.6 as a temporary test. These should eventually go away, but
in the meantime, skip running these on things like docs changes.
Change-Id: Idc42028d4c31d9ee31cdcea11b8749fffa5007b4
Create a tox environment for running the unit tests against the lower
bounds of the dependencies.
Create a lower-constraints.txt to be used to enforce the lower bounds
in those tests.
Add openstack-tox-lower-constraints job to the zuul configuration.
See http://lists.openstack.org/pipermail/openstack-dev/2018-March/128352.html
for more details.
Change-Id: I329e6364d537f2acac796e389f15f3c7162a9244
Depends-On: https://review.openstack.org/555034
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This is the only job that tests Cinder+Barbican
integration.
It should be voting, as this is vital for users of
encrypted volumes.
Change-Id: I1b2e29da5d25aefe9183660820ab759c65301e30
We have functional tests that run under py35, but they are not
currently run in gate. This adds the common job definition to
our locally defined list of tests to run.
Change-Id: Icf477415c7ac54bb007cacc1a1ba905e63fa2780
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: I881e1a8d4e2fca0f534144b4a1826f431464c25f
The nova-multiattach job is defined in the nova repo
but we also need to run it against Cinder changes.
For now the job just runs the tempest compute API tests
since that's the only place in Tempest that has multiattach
testing right now and it will save some time in the CI run.
Change-Id: Idfb68b5ddd7aca8642016e392fec6efd169c1ea2
Depends-On: I51adbbdf13711e463b4d25c2ffd4a3123cd65675
The compliance and bandit-baseline jobs just call tox to run tests.
These are an easy step to move in-tree.
Since it is also easier to have conditions on when things run, this
also adds filtering so the compliance job will now only run when there
are changes in code that impact the drivers.
Change-Id: Idb9a1f39481f3ebb704b28abc062ae24414d7224
Needed-by: I3af7771ab3e8d5a192f466dcec36a2b41db08ac3
Needed-by: I4af1813c69a5ddccbde8b99ed15023aa407995b5