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: Ie4dacf5ecb567f29a93b998b89b97ea874e02fda
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
tesitng[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: I79c6c5a676695b22135b21f8b4837f77bd2eb876
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: If8b9af02d1035bd1fa1e5cf8c307784e8e8d36f2
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.
Also fixing the zuul config error.
[1] https://governance.openstack.org/tc/goals/selected/migrate-ci-jobs-to-ubuntu-jammy.html
Change-Id: I1d4b8d50d6286cf90fd41c5ab95161bad7cd6df3
The 'all-plugin' tox environment was deprecated by this patch [1].
Instead of the 'all-plugin' it is recommended to use the 'all' tox
environment.
This patch removes any reference to 'all-plugin' tox environment and
updates the documentation so that the installation steps work with
the 'all' venv.
[1] https://review.opendev.org/c/openstack/tempest/+/543974
Change-Id: I29e2f542de8358908bded2e843adaeb4b1c12ace
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: I11bfd3026a02bad7cb6336ed66e7d1ef8559d5af
orchestration_client is recently moved from tempest
to murano-tempest-plugin but there is one import error
and instantiation of orchestration_client. Fixing the
error.
Change-Id: I0743a6c1e9a97740aa5e5cb7f10bc0f06aabbf05
orchestration_client in Tempest is planned to be removed and heat
client present in heat_tempest_plugin is supposed to be used
- ba43685c13/heat_tempest_plugin/services/clients.py (L103)
Meanwhile murano_tempest_plugin is the only user of tempest orchestration_client
so moving that here and it can be removed once murano switch to use
client from heat_tempest_plugin.
Change-Id: I8f160c6b9b59d6915d6fb346be7816b4b8084939
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: I9c5984e7caabf61c10b9d211a5347799701bf3e1
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: I41705ea681578cfdc510052122abec4838d8c578
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: I82edeeac54ad53bcafe8e77ceb8aef382fce5748
As per victoria cycle testing runtime and community goal[1]
we need to migrate upstream CI/CD to Ubuntu Focal(20.04).
Most of the Tempest jobs will be migrate automatically once devstack
base job start running on Focal(Depends-On).
Stable jobs testing stable branch needs to keep running on their supported
distro version which is bionic from stein till ussuri.
[1] https://governance.openstack.org/tc/goals/selected/victoria/migrate-ci-cd-jobs-to-ubuntu-fo$
Change-Id: I72f42951d29a23d01fbe803d553debc76d49acbc
Story: #2007865
Task: #40198
Congress has been retired and requirements-check fails now, remove
congress.
See also https://review.opendev.org/721741
Change-Id: Ic2d74543f65a60ccb567aae4c4012c422884bb50
Switch to openstackdocstheme 2.2.1 and reno 3.1.0 versions. Using
these versions will allow especially:
* Linking from HTML to PDF document
* Allow parallel building of documents
* Fix some rendering problems
Update Sphinx version as well.
Disable openstackdocs_auto_name to use 'project' variable as name.
Change pygments_style to 'native' since old theme version always used
'native' and the theme now respects the setting and using 'sphinx' can
lead to some strange rendering.
openstackdocstheme renames some variables, so follow the renames
before the next release removes them. A couple of variables are also
not needed anymore, remove them.
See also
http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014971.html
Change-Id: Ifff5d0860f0c9e68a0187242335c5bf7c383a486
flake8 new release 3.8.0 added new checks and gate pep8
job start failing. hacking 3.0.1 fix the pinning of flake8 to
avoid bringing in a new version with new checks.
Though it is fixed in latest hacking but 2.0 and 3.0 has cap for
flake8 as <4.0.0 which mean flake8 new version 3.9.0 can also
break the pep8 job if new check are added.
To avoid similar gate break in future, we need to bump the hacking min
version.
- http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014828.html
Change-Id: I2992185abe1971dfa3afed4836cdb29cd245e47c
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: If109a13873d2ee9ede112952056914dc4c57b4df
Update docs building:
* Switch to sphinx-build
* Update requirements for Sphinx and openstackdocstheme for
python 3, create doc/requiremetns
* Remove unneeded doc and translation sections from setup.cfg
* Remove install_command, it's unneeded, the default is fine.
* Move constraints to deps, use TOX_CONSTRAINTS instead of obsolete
UPPER_CONSTRAINTS
* Remove now unneeded placeholder file
Change-Id: I649e6fa86c17262698cc8a01d042a87b020239d9
Make a few cleanups:
- Remove python 2.7 stanza from setup.py
- Add requires on python >= 3.6 to setup.cfg so that pypi and pip
know about the requirement
- Remove obsolete sections from setup.cfg:
* Wheel is not needed for python 3 only repo
* Some other sections are obsolete
- Update classifiers
- Update requirements, no need for python_version anymor
Change-Id: I3f780c21e6867a394e1797e67099f1668388f6a7
The repo is used on older branches as well, and new hacking supports
only python3.
We really only need hacking on master anyways,
where we no longer support python 2, so here we
make the requirement specific to python 3.
Change-Id: I3734c7d345832110dd7db8a0d0d7ff65e2a9a757
The repo is Python 3 now, so update hacking to version 2.0 which
supports Python 3.
Fix problems found.
Update local hacking checks for new flake8.
Change-Id: I2683bc1a7c962da137de4b77aac450f08d1f6c4a
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: Ib934cd24f4af8440458f0d24df90b77e0a3040b5
In scenario test, test packages will be uploaded and then deleted after test
executed. But in case of the packages deletion failure, it will block the
following tests.
This patch checks and removes those test packages before uploading them.
Change-Id: I90c5d903d8c5c3eeface2735bba61d01a877aaf8
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.
Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.
Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: I2dee7ac8ba73bbf61776fd34c3f9172b425b6873
Story: #2002586
Task: #24313
* tempest.lib.decorators provides a better way to handle attrs, let's
use it instead of using nose from tempest.lib stable api.
Change-Id: Iad64bbaac517b8e1f53ec7046691a79e63f4f74d