Add stable/pike on tempest-full.
The job will be voting on stable/pike so we need bitrot
jobs on Tempest master as well. Not the py3 since it was
not running on Pike yet.
Once this lands we can add bitrot jobs to d-g as well,
and filter the legacy job out of pike in the integrated
templates.
Depends-on: https://review.openstack.org/545258/
Change-Id: I1ac0e54eab22786575e11f4d34b7e15e643038c4
This removes the outdated comment in .zuul.yaml. We already have not
only master branch job but also stable/queens now. And we don't have
the negative lookup anymore.
Change-Id: I8c66502832250a00c4ec1e7c89387d67fa093e0d
Use the override-checkout feature at job level to get all branched
repos from stable/queens. Define both py27 and py3 jobs.
Change-Id: I81e63e690512e6b6eacf3d255feaf73a425d957e
Now that tempest-full-py3 is in the integrated gate there's no need
to have it again in tempest local .zuul.yaml check.
Change-Id: I10861232d9af772acb419fa10c590e13fb8a8fbc
stage-output is already invoked in the devstack job.
Rather than running the role again in Tempest post, extend the
list of files to be staged and extensions to be converted to txt.
Change-Id: I0844700f1c770809cba5a2e0e39737fd6827896f
Depends-on: https://review.openstack.org/540485/
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: I34872b5c9a2ed82a8dd1e7112453c0d99cb5e0ba
The nova-multiattach job is defined in the nova repo
but we also need to run it against Tempest 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 job is ready to replace the legacy one in the integration
gate py3 template. Before that can happen make it voting and add
some extra documentation to it.
The parent does not need to be tempest-full since that does not
add much useful as opposed to devstack-tempest and it's actually
better for the two jobs to be independent.
Change-Id: I4a8fa1759665038788e1b86fd3a5030fd6c68573
For consistency with the tox jobs, use tox_envlist instead of
tox_venvlist. See
https://docs.openstack.org/infra/zuul-jobs/jobs.html#job-tox for
definition of tox job.
All projects using tox_venvlist have been changed to use tox_envlist as
well (see dependencies). Now we can rename tox_venvlist to tox_envlist -
and then the projects can remove tox_venvlist and use only tox_envlist.
Change-Id: I67a20b1faa77ff0166ad96fd95432c11948abc74
Depends-On: I035584aaeaa71b62c1d0c7e0a62dbf053a3488b6
Depends-On: I2fb02ead3b45c2a05d28f59fd28d062a3b40e07e
Depends-On: Id03d4c1351d5a002dc9d73247d0315bef274f627
Depends-On: Iff3093e61c7d2cb684667d5bc5f2a75580569aab
This condition was added to openstack-zuul-jobs in [1], but it created
bug #1739829 as a side effect. While addressing the issue [2] it was
noticed that conditional could be located in the tempest repo itself,
so this patch aims at cleaning things up a bit and reduce the moving
parts.
[1] I799ea86f3c445bb067950a8cbc237999d621e3a9
[2] I5d34e5b983b720dc1913d00ccc1a16d81a040d49
Needed-by: Ibfbc925af6eb274ced53312301b1733136ba4455
Partial-bug: #1739829
Change-Id: I8e0aa11cd2d92d5d6f5e9147a407374948920e7f
tempest-full is now part of the integration-gate, so it doesn not
need to be in the local .zuul.yaml anymore. Besides it was marked
as non-voting which should not be the case.
Change-Id: I14e8b10789ebb8a20c400099ce4d861979f701a2
Setup the tempest-full in Tempest job configuration.
The job as it looks now does not match its legacy counterpart, but
all of the features missing are on devstack side:
- selection of enabled services based on matrix
- collection of logs and configuration files
Change-Id: I387950424d25db9b671b077b47b14197683f5f66
Create a zuulv3 native job to replace the existing legacy tempest plugin
sanity check. The tempest plugin sanity script has been modified to fail
if at least one of the plugins failed.
Related fixed in plugins:
* Id08618a497b0f9205680a97d31600481b92eab08
* I3de3d6c6928d31af9c2deeba800b201bb681ac4e
Change-Id: I2bd52892b05d5c4044e11a34b2ca150dd2445c07
Stage three tempest conf and log files for archival using the
stage-output role.
Depends-on: Id45a50821539985710da7172a9185fd91e803603
Change-Id: Id67dbf3df5af52e848b8d378bc13aaa1c02cdd29
Setup the initial folder and play to run tempest.
This simply runs tempest full for now, with not support for config
options.
Change-Id: I5a76dd23900a1b5fb1764fafd837d69baf9ed8b1
Depends-on: Iffe54fbccbccd68db08f79a1b51dd7f76dbff408