We don't really have unit tests in the repository and any py3x venv
would not really be useful (the tests are executed through tempest),
but let's remove the old dependency anyway and depend on stestr
like all the other OpenStack projects.
Change-Id: I52d06f1c1e141cb455fb7a823a27be532afb4c16
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: I166c9479d94a42114adc94778140a9878a5949c5
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: Ic84db0e885c6560120548ecb2ebc16dde1cd23d1
This repo is now testing only with Python 3, so let's make
a few cleanups:
- Remove python 2.7.3 stanza from setup.py
- Remove obsolete sections from setup.cfg
- Remove install_command from tox.ini, the default is fine
- Switch to hacking 3.0, ignore W503 and W504 (as in cinder repo)
- Use TOX_CONSTRAINTS instead of obsolete UPPER_CONSTRAINTS
Change-Id: Ia623c8af7f03c25bce7e4600693a7e834ab70000
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
3. Remove unncessary "=="
Change-Id: Iff24e8d5082d8ef8dc2d29ea92288bf418f5500d
Minor cleanup of things not needed for our tempest plugin.
Change-Id: Ib309cb1f87211e82eae0d27fa2464ec13a9deca6
Needed-by: I5ff95ca13f02ed6e0afb35f0d6bb5c36d4111f5a
Implements: blueprint goal-split-tempest-plugin
This tempest plugin is being split out of the main keystone project in
accordance with Queens goal "Split Tempest Plugins into Separate
Repos/Projects"[1]. This patch applies the standard boilerplate files
for OpenStack projects so that it can stand on its own.
[1] https://governance.openstack.org/tc/goals/queens/split-tempest-plugins.html