Add file to the reno documentation build to show release notes for
stable/2023.2.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2023.2.
Sem-Ver: feature
Change-Id: Ib01f17310f6828d3dec06abd0b4838ccfd990708
Add file to the reno documentation build to show release notes for
stable/2023.1.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2023.1.
Sem-Ver: feature
Change-Id: I736f31968a913de631e86d1fbd88f2662f0c9847
OpenStack CI now uses tox4 by default.
- Drop "skipsdist = True".
When skipsdist=True is specified, a target application is not
installed into a tox env, but there seems no reason to do so.
In various other OpenStack projects, a target applicatin needs
to be installed into a tox vnev, for example, in docs and/or
linter jobs and it causes failures with tox4. So dropping it
would avoid potential future failures.
- Add ignore_basepython_conflict = True to tox.ini
With latest tox (>4.0.15) python version conflicted with base
python. Adding ignore_basepython_conflict = True solves this
issue.
Change-Id: Id25cde435e9eaf6d5d2573d522cda763dad1a89b
inspect.getargspec was deprecated since Python 3.0 and
inspect.getfullargspec is its replacement with correct handling of
function annotations and keyword-only parameters[1].
[1] https://docs.python.org/3/library/inspect.html#inspect.getargspec
Co-Authored-By: manchandavishal <manchandavishal143@gmail.com>
Change-Id: Ie9cdf3e87a06a0af8cf36c8bbdef0f14336e8f70
This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for antelope. Also,
updating the template name to generic one.
See also the PTI in governance [1].
[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html
Change-Id: Id599fb692f5a36f8dba39ca98abe5ac54b707b56
Add file to the reno documentation build to show release notes for
stable/zed.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/zed.
Sem-Ver: feature
Change-Id: I3f5f9bd3fdd591cc836895a0998708fa7cf656d0
Add file to the reno documentation build to show release notes for
stable/yoga.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/yoga.
Sem-Ver: feature
Change-Id: I58a438faadd070ec8ec868c4eaee2ef7f17904bc
Add file to the reno documentation build to show release notes for
stable/xena.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/xena.
Sem-Ver: feature
Change-Id: Iee515e29541c6957db520339fa923a59a392ff6e
Coverage report job for watcher dashboard must have been
broken for an extensive amount of time. This patch
fixes it.
Change-Id: I3f0ec731d28d0f55c4378038237dc91b5c548ed5
The name is a positional parameter in create() of audit,
but this parameter is not defined when calling from the
audit template. This patch fix it.
Related Bug: #1930565
Change-Id: Id18945b881d150f972dbbd5522010be0157fba17
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: I0573f72eb92ddda5392dbf78260a18b17a8d75af
We facing errors related to the new pip resolver, this
topic was discussed on the ML and QA team proposed to
to test lower-constraints [1].
I propose to drop this test because the complexity and recurring pain needed
to maintain that now exceeds the benefits provided by this mechanismes.
[1] http://lists.openstack.org/pipermail/openstack-discuss/2020-December/019390.html
Change-Id: I9308030b0a16f9a7e085b3e64230cd92dda6ad83
Add file to the reno documentation build to show release notes for
stable/wallaby.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/wallaby.
Sem-Ver: feature
Change-Id: I4b5dbd04eeef670f66b567e380cb15cd6547aee6
Add file to the reno documentation build to show release notes for
stable/victoria.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/victoria.
Change-Id: I861430e8f0d3acee6ea6e94aa84ca7e2442d0714
Sem-Ver: feature
This patch is a clean-up patch for refactor-error-messages bp
which remove the exception message from base message otherwise
the same exception message display twice like
this https://ibb.co/XyFWMdz .
Depends-On: https://review.opendev.org/#/c/708069/
Change-Id: I3ff5f7b25c0e91e67a8c98020993676d6345379e
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.
Set openstackdocs_pdf_link to link to PDF file. Note that
the link to the published document only works on docs.openstack.org
where the PDF file is placed in the top-level html directory. The
site-preview places the PDF in a pdf directory.
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.
Remove docs requirements from lower-constraints, they are not needed
during install or test but only for docs building.
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: Ie14b87a1e67a7b4351f17a2f0687bcfe5a4b2133
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: Ia4747715db8e70d66087dfc0c2b723c451b321a0
1. Now that we no longer support py27, we can use the standard library
unittest.mock module instead of the third party mock lib.
It also update horizon dependency in lower-constraints.txt.
2. remove six together
Change-Id: I371e7485438d43eb823ab7d4fd719e0e52da75eb
Now that we are running the Victoria tests that include a
voting py38, we can now add the Python 3.8 metadata to the
package information to reflect that support.
Change-Id: I5fcc63ab2ad9a6c5f9cd1a922ef7ea5627c7a396
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Add file to the reno documentation build to show release notes for
stable/ussuri.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/ussuri.
Change-Id: I8d45faee435c6368707577f17a5f136343bea810
Sem-Ver: feature
This repo is now testing only with Python 3, so let's 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
- Update classifiers
- Update requirements, no need for python_version anymore
- Switch to using sphinx-build
- Cleanup */source/conf.py to remove now obsolete content.
- Use newer openstackdocstheme version
- Use mock from unittest;leave it in test-requirements for now since
otherwise lower-constraints fails since some repos expect mock to be
installed without requiring it.
- Remove future imports, not needed for python3
- Update to newer hacking version for python3, disable one warning.
Remove hacking requirements from lower-constraints, they are not
needed there.
- Cleanup tox.ini, move basepython to top
- Update horizon requirement for ussuri
Change-Id: I1753bce3ac4fc4248783c0669cacab2e037e62fe
Horizon requires pyScss>=1.3.7 [1] but lower-constraints.txt
in watcher-dashboard uses pyScss 1.3.4 which can cause the
failure in future. So this patch update pyScss version in
lower-constraints.txt to sync the change.
[1] https://review.opendev.org/#/c/715241/
Change-Id: Ied17533efae12a4c8cac0b259c88d2d43dff2afa
assertItemsEqual was renamed to assertCountEqual in Python 3, and the
testsuite is failing now - rename it.
See also https://six.readthedocs.io/#six.assertCountEqual
This unbreaks the testsuite.
Change-Id: I4c9d3d1f6a5566f46b00f69d8f45487472405ffe
Django 1.11 ends its extended support in April 2020 (which is before
Ussuri release), so horizon drops Django 1.11 support in Ussuri.
tox envs for non-primary Django versions are no longer needed in tox.ini
as testing environments for non-primary Django versions are setup in
the zuul jobs now.
horizon>=17.1.0 is required to use Django 2.2. requirements.txt and
lower-constraints.txt are updated accordingly. for more info. please
refer [1].
Depends-On: https://review.opendev.org/#/c/700733/
[1] https://etherpad.openstack.org/p/Enable_Django22_support_in_Horizon_Plugin
Change-Id: Ib5ea9d22170b9d0285a74c6e4924fd4b6e9f4eb8
babel extractors are now registered via python entry points,
so there is no need to declare babel extractors in babel configs.
This change is important to make translation work in Django 2.2.
django-babel does not work with Django 2.2 and looks unmaintained
for over two years. The horizon team is thinking to switch the extractor
to enmerkar (a fork of django-babel) to make extraction of translation
string work again near future. It is important to drop the extractor
definition to make the transition smooth.
Change-Id: I17553cc99a4b2d63b5ae8669e431bcb352f278bc
1. Sphinx 1.8 introduced [1] the '--keep-going' argument which, as its name
suggests, keeps the build running when it encounters non-fatal errors.
This is exceptionally useful in avoiding a continuous edit-build loop
when undertaking large doc reworks where multiple errors may be
introduced.
2. pbr hasn't need the hook configuration since forever [2]
[1] https://github.com/sphinx-doc/sphinx/commit/e3483e9b045
[2] c84876dc0f
Change-Id: I421c88c7c5d2b494443986607e9ddfb87c02bc72
OpenStack Release Bot
Zuul