As per the current release tested runtime, we
need to test till python 3.11 so adding the test
and updating the same in python classifier in setup.cfg
Change-Id: Ib3ceb518a7953e192c33dd2dc48d84bbaf5e4395
The template which is used to test runtime for the Zed cycle added
python 3.10 as a non-voting job [1]. So this patch follows the same
thing here.
[1] https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/831633
Change-Id: I6d96cf6e3702aaadb22d17c23306156d23baaa0d
In Yoga testing, we are making py3.9 job to run as voting, so
adding py3.9 job as voting.
Also, as devstack-tools is branchless and needs to support older
supported stable branches, let's test it with all the
python version supported in those supported stable branches.
For that, we need to explicitly dd the py jobs instead of using
the template. This way, we will explicitly know that we are testing
all supported python versions when the new release template bumps the
min python version in the template.
Change-Id: I21ecaf1d3f627ae27a217d7fa2326f7dd69242c9
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
Change-Id: I3d433b146f699e005aeef74cd763d95dc8a1b4bd
* Replace .testr.conf by .stestr.conf for migration and update
.gitignore and test-requirements.txt file accordingly
* Use py3 as the default runtime for tox
* Add a new job, openstack-cover-jobs, to run the coverage in Zuul
Signed-off-by: HeroicHitesh <email.hiteshkumar@gmail.com>
Change-Id: I72eebd8adfa2086b7d3a11eedbfe2e69cfd65bcc
This patch enables building .pdf documentation using new 'pdf-docs'
tox environment. The newly created tox environment creates latex
source codes using sphinx-build and then builds the pdf
documentation using make.
Story: 2006070
Task: 35460
Change-Id: I1f0ca39747e8ef95d2b93cd00214911d4a7408a9
This repo is now testing only with Python 3, so let's make
a few cleanups:
- Remove python 2.7 stanza from setup.py
- Remove obsolete sections from setup.cfg
- Update classifiers
- Remove install_command from tox.ini, the default is fine
- Remove babel.cfg, it's not needed anymore.
- Use TOX_CONSTRAINTS_FILE, UPPER_CONSTRAINTS_FILE is obsolete
Change-Id: I235cf10f6a619fa6c41e688a17337385a1034aa2
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_auto_name to use 'project' as name.
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.
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.
See also
http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014971.html
Change-Id: If718e3d21c682dd3a3d297cfa9cebb333d59aef3
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: I7c9c0dc296ac374881c03fcaa6c886e38f3d5d14
This commit adds publish-openstack-docs-pti job to .zuul.yaml to verify
the rst files. To build the document, this commit also updates doc
related things such as requirements.txt, conf.py and the docs task in
tox.ini.
Change-Id: I4d1378a1972cad6f965d5cac6567d56828f75fb7
The repo is Python 3 now, so update hacking to version 3.0 which
supports Python 3.
Fix problems found.
Change-Id: Ia1bbe6bd173435674075bee595001a7e8aa0d4ec
We want to default to running all tox environments under python 3, so
set the basepython value in each environment.
We do not want to specify a minor version number, because we do not
want to have to update the file every time we upgrade python.
We do not want to set the override once in testenv, because that
breaks the more specific versions used in default environments like
py35 and py36.
Change-Id: I15eb789db64c58865fc3dae99a7e83f90c971a60
Closes-Bug: #1801657
We want to default to running all tox environments under python 3, so
set the basepython value in each environment.
We do not want to specify a minor version number, because we do not
want to have to update the file every time we upgrade python.
We do not want to set the override once in testenv, because that
breaks the more specific versions used in default environments like
py35 and py36.
Change-Id: I6faa7c3e39f02d765d7ceed4a69490b2092c6fee
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
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: I2f0d88f88d36347bcc9702be74ab9812dc78842c
Story: #2002586
Task: #24327
Previously the logic around hitting the end of the file without having
found the insertion point didn't account for the fact that you might
be in roughly the right area, and would not need to duplicate the meta
section or section headers.
This takes that into account during the else phase. It will help with
the neutron functional jobs that merge a lot of snippets together.
Change-Id: Ifaa1176e9fdfbc4fdb43192ed2f85e7306823848
Previously if we tried to added content to a local.conf file without a
local section, we actually inserted that content in the wrong place at
the end of the file. This fixes that, with unit tests.
Change-Id: Ib886d78ce5f3718def784db59ba9abf41bdb0e7b
setlc_raw can be used to set several lines at once. The test checks that
it works as expected. See I565f5420743fbd95e9d744010c488953c54dd8a4
for some context of why that is useful.
Change-Id: I21bd78fa6169002a70fa9074d56d985bfc0b833f
the localrc is really just executable shell, which means there are
tons of edgecases where you can't treat it the same as simple
assignment a=b.
Instead of trying to be smart about things and reduce duplication in
the localrc files, just do the naive thing and stack up all the shell
declarations in order. When evaluated in shell they will end up
stacking up as expected.
Change-Id: I231d130b24b02cdd79618f85472cee21905884e0