Also remove outdated warning about package order and remove pyflakes
requirement, as described in the comment.
Also disable the failing stable/2023.1 job, which will be removed in
another change.
Change-Id: I60c34d04f0a6773435504e585e3afe468973a921
As 2024.2 is released, we should add its job on master
gate to keep branchless tempest plugins compatible
to stable branch.
Ref: Tempest plugins guide for stable branch testing:
- https://docs.openstack.org/tempest/latest/stable_branch_testing_policy.html
Change-Id: I7f30edc9b5976e5942e906036d1eda7b49c417d4
As per the current release tested runtime, we test
from python 3.9 till python 3.12 so updating the same
in python classifier in setup.cfg
Also, dropping the python3.8 support
- https://lists.openstack.org/archives/list/openstack-discuss@li>
Change-Id: I370490bc405c2a81a4822e6bd1d86dfee5fc6e60
The zed series has gone to Unmaintained status and the stable/zed
branch has been deleted in cloudkitty project, so remove the
associated jobs.
Change-Id: I8fc4c4c4334a4a85917bdfa79c506d9cb1f22633
As 2024.1 is released, we should add its job on master
gate to keep branchless tempest plugins compatible to stable branch.
Also, fixing a few of the stable/2023.2 jobs to override-checkout 2023.2.
Ref: Tempest plugins guide for stable branch testing:
- https://docs.openstack.org/tempest/latest/stable_branch_testing_policy.html
Change-Id: Ic3e3dc069c739dc8794c9b0e97079037f76c1429
As per the current release tested runtime, we test
till python 3.11 so updating the same in python
classifier in setup.cfg
Change-Id: I70bb082db82af9dabd854088700c9263a0bc0faf
As 2023.1 is released, we should add its job on master
gate to keep branchless tempest plugins compatible
to stable branch.
Ref: Tempest plugins guide for stable branch testing:
- https://docs.openstack.org/tempest/latest/stable_branch_testing_policy.html
Change-Id: Ic55417d33e0ab4f5ede51b92f9d91e5befc60107
This repo is now testing only with Python 3, so let's make
a few cleanups:
- Remove python 2.7 stanza from setup.py
Change-Id: Iffda38282f00020b7b4da690217b9cddd13ab0c7
stable/wallaby is in EM state. As Tempest and
plugins masters does not support EM stable branches,
QA team is pinning tempest in devstack stable/wallaby
testing[1]. With that we do not need to test the
stable/wallaby jobs on master gate.
[1] https://review.opendev.org/c/openstack/devstack/+/871782
Change-Id: Ie7db6b07101db8c5a48cf5ad13be7ccf7278b52e
As zed is released, we should add its job on master
gate to keep branchless tempest plugins compatible
to stable branch.
Ref: Tempest plugins guide for stable branch testing:
- https://docs.openstack.org/tempest/latest/stable_branch_testing_policy.html
Change-Id: Idb8cf4124db69758d71e07b139422b5afafcef78
In 2023.1 cycle. we are moving the default distro
version of Ubuntu to Jammy (22.04)[1] so we need to pin
the nodeset for stable branch job in master gate so that
they continue run on their supporting distro version which is
Ubuntu Focal since stable/victoria.
[1] https://governance.openstack.org/tc/goals/selected/migrate-ci-jobs-to-ubuntu-jammy.html
Change-Id: I986dc439249c9f31b72c8be5376e4b1f7566b2d3
stable/victoria is in EM state and Tempest is pinned
there so we do not need to test the stable/victoria
jobs on master gate.
Change-Id: Ia10922e946c06f936bb7062086f110f225c17b46
We have stable/yoga released and stable/ussuri is in
'Extended Maintenance' state. Current 'Maintained'
stable branches are yoga, xena, wallaby, and victoria.
As per tempest stable branch testing policy[1], adding the
newly released stable/yoga job and remove the EM stable/ussuri
job.
[1] https://docs.openstack.org/tempest/latest/stable_branch_testing_policy.html
Change-Id: Ice08a4c26ae88359b958e9eb7e3044c6dd3f13a5
We have stable/xena released so we should add
their job on master gate to keep branchless tempest
plugins compatible to stable branch.
This also removes the stable/train job as that is in EM
state now.
Ref: Tempest plugins guide for stable branch testing:
- https://docs.openstack.org/tempest/latest/stable_branch_testing_policy.html
Change-Id: I18f469a60f70afeffa470dbf9db56b64871607f1
UPPER_CONSTRAINTS_FILE is old name and deprecated
This allows to use upper-constraints file as more
readable way instead of UPPER_CONSTRAINTS_FILE=<lower-constraints file>.
Change-Id: I378644df79feae8f90b4eba60bb979f5c9fbc60a
Setuptools v54.1.0 introduces a warning that the use of dash-separated
options in 'setup.cfg' will not be supported in a future version [1].
Get ahead of the issue by replacing the dashes with underscores. Without
this, we see 'UserWarning' messages like the following on new enough
versions of setuptools:
UserWarning: Usage of dash-separated 'description-file' will not be
supported in future versions. Please use the underscore name
'description_file' instead
[1] https://github.com/pypa/setuptools/commit/a2e9ae4cb
Change-Id: I47bfd89850444ba894f54d373658bea2a1573ac0
We have stable/victoria and stable/wallaby released so we
should add their job on master gate to keep branchless
tempest plugins compatible to those branch.
This also removes the stable/stein job as that is in EM
state now.
Ref: Tempest plugins guide for stable branch testing:
- https://docs.openstack.org/tempest/latest/stable_branch_testing_policy.html
Change-Id: I2bd157aab1ec857fcb2acc0dcffc23b0cf1bab8f
We need to specify doc requirements in doc/requirements.txt
to avoid problems with the pip resolver [1] for the release team [2][3].
Removed specific doc requirements from test-requirements.txt.
The problem here is that this repos haven't doc/requirements.txt file
and by default in this case zuul will use the test-requirements.txt file
to pull requirements [4].
This requirements file contains extra requirements like flake8 that
collided with those allowed in our job environment and so the new pip
resolver fails to install these requirements and the job exits in error.
This project meet the conditions leading to the bug however it doesn't
produce any doc or releasenotes, but uniformization can't hurt and help
us in the future.
/!\/!\/!\
Notice that I voluntarily added the doc directory even if no docs
are generated here because zuul will try to pull this requirements from
there first and the contained requirements are needed for reno but AFAIK
the releasenotes dir is ignored by zuul. c.f [4] for further details.
/!\/!\/!\
[1] http://lists.openstack.org/pipermail/release-job-failures/2021-January/001500.html
[2] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019611.html
[3] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019612.html
[4] https://opendev.org/zuul/zuul-jobs/src/branch/master/roles/ensure-sphinx/tasks/main.yaml#L36
Change-Id: I18fdf133b6c3ea9b60e784c0e1dfb7ce1217eda5
tempest.Manager has been deprecated for more than 4 years already
and will be removed by [1].
Tempest plugins are expected to consume
tempest.lib.services.clients.ServiceClients directly.
[1] https://review.opendev.org/c/openstack/tempest/+/767628
Change-Id: Ibd04c38c084f63e9129f0bfef1df988e410695db
pep8 job is failing because the version of flake8
(flake8<2.7.0,>=2.6.0) requested by hacking<1.2.0 is not
compatible with pyflakes>=2.1.1. Therefore the patch increases
the max version of hacking.
Change-Id: I04635509cc8b794f9aaad8ac43a25bf6ddd9b9e1
Supported stable branches in maintenance state
(stein, train, ussuri) use the Tempest and plugins master
version for their testing. To make sure master version (new
tests or any changes) is compatible with stable branch testing,
we need to add the stable branches job on the plugins master gate.
Tempest and many other plugins are already testing the stable
branches in same way[1].
Ussuri onwards, Tempest or plugins are py3 only, so we are
running only python3 version of stable jobs
Tempest plugins guide for stable branch testing:
- https://docs.openstack.org/tempest/latest/stable_branch_testing_policy.html
[1] e8f1876aa6/.zuul.yaml (L646)
Change-Id: Ib55ee338e788fe9c529bdc0f12bc91899d6c8618
This commit removes .testr.conf since this repo already has
.stestr.conf. We just need .stestr.conf instead of .testr.conf.
Change-Id: Ia718139547f7435db3146fd8a9cb6f9a40185f52
This commit cleanup requirement file and add
ignore_basepython_conflict flag into tox to avoid
python version conflct.
Change-Id: Ie7a80ac58dc425e66cf2b7334b99e22a07759dbc
This drops python2.7 support for cloudkitty-tempest-plugin. The lowest python
version now supported by cloudkitty-tempest-plugin is 3.6.
Depends-On: https://review.opendev.org/#/c/694434/
Change-Id: I2b4a57dae3f150b22c38cc2b83747ee4231b31fe
For convenience we split the tests between the two current versions
of CloudKitty.
Change-Id: Ib10a6ffe9e0dd6c628f05588b463230139bf42c8
Story: 2006578
Task: 36895
This updates the cloudkitty tempest jobs. Work items:
* Rename existing jobs
* Add jobs introduced by https://review.opendev.org/#/c/679085/
Change-Id: Iec6ae6ca8ff1d4f956081daed08d8ae534fa10aa
1. Sync sphinx dependency with global requirements. It caps python 2 since
sphinx 2.0 no longer supports Python 2.7.
2. Update some URLs to latest
Change-Id: I6c1ed891087602ec0a9bf8b53445fa4aef2b1f6c
