Removes and/or replaces all mentions of py27.
Cleans up obsolete requirements and their lower-constraints.
Change-Id: Id43f1bbd6a454832ab8dbf003a058403f6b34b5d
We don't need tox nor tell our users to use it when doing kolla builds.
Tox is going away from base infra images (it is already gone from
aarch64 ones).
Depends-on: https://review.opendev.org/713134
Co-authored-by: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Change-Id: Ib1d97a783951ac42740ebf91bcc6ecaf2bf70853
The repo is Python 3 now, so update hacking to version 3.0 which
supports Python 3.
Fix problems found by updated hacking version.
Update local hacking checks for new flake8.
Remove hacking and friends from lower-constraints, they are not
needed in installations.
Change-Id: I67e5ca24c550163c218fb06692de0b7c528d8318
Cleanup requirement and set ignore_basepython_conflict = True
in tox to avoid python version conflict warning which going
to be error in future.
Change-Id: Ia749d558df33f475dfdbe7a1f9dfdb30aeba8da0
2020 came, everyone should be using Python 3 now.
As per the official python support timeline set forth
by the OpenStack TC [1], OpenStack Train (in our case,
kolla 9.x) is the last release that will support python2.7.
[1] https://governance.openstack.org/tc/resolutions/20180529-python2-deprecation-timeline.html
Related bug: https://bugs.launchpad.net/tripleo/+bug/1856678
Merging depends on TripleO team - once they move CI job to CentOS 8 we
can merge.
Implements: blueprint drop-py2-support
Change-Id: Ic459561ab6ab8c62993c044c7a82d887839da289
Adds build and publishing jobs for CentOS 8 images:
- kolla-build-centos8-binary
- kolla-build-centos8-source
- kolla-publish-centos8-binary
- kolla-publish-centos8-source
The 'base' image has been added to the list of unbuildable images for
CentOS 8 (now separate from the list for CentOS 7). This means that no
images will be built - the jobs should essentially be a 'noop'.
Change-Id: Ie9a0109bd4eef337358d714e4b5088b8e3de2f23
Partially-Implements: blueprint centos-rhel-8
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.
[1] https://github.com/sphinx-doc/sphinx/commit/e3483e9b045
Change-Id: I6b8897472220e2f45ec3230be8d3f82adacc7c7e
If stestr failed, then no node info was logged.
Logging node info is now handled in pre and post stages of Zuul.
Additionally Zuul v3 migration recommendations were applied
and some unused code removed improving general readability.
Change-Id: Iae9d37cb76997ba8389e21c7e2a3bf5905abe029
Signed-off-by: Radosław Piliszek <radoslaw.piliszek@gmail.com>
According to Openstack summit session [1],
stestr is maintained project to which all Openstack projects should migrate.
Let's switch to stestr as other projects have already moved to it.
[1] https://etherpad.openstack.org/p/YVR-python-pti
Change-Id: I27308a2435a4dca572d736f56a02b0bbc8563981
python 3.6 pycache also includes links - so those also
need to be removed
Depends-On: https://review.openstack.org/636750
Change-Id: I0f995df45bf203acc79cc7bd52b9ac51577468da
Change order of default tox envlist in order of likeliness to fail on a
new change and add py37 and py36.
Change-Id: I7b88f0ebce37a319e66b20d5438852976195f06e
This is a mechanically generated patch to add a unit test job running
under Python 3.6 as part of the python3-first goal.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: I37bd6b96781ad8ca47c5cd57f455c540245f27f0
The commands used by constraints need at least tox 2.0.
Update to reflect reality, which should help with local running of
constraints targets.
Change-Id: Ie74cd61e251d46524d83a05c0b48fd462aeb4a57
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: I916dfe05c88d3960e0239a6b9a7e5affc6d79196
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Fix yaml warning in release notes. And this patch wants to
make sure pep8 jenkins job can cover yaml warning check
in the future. So use yamllint with strict mode[1]
to treat warning as error.
[1] http://yamllint.readthedocs.io/en/stable/configuration.html#errors-and-warnings
Closes-Bug: #1778389
Change-Id: I05af5204c4d5388daa8bd3c8582fd1058df15920
Create a tox environment for running the unit tests against the lower
bounds of the dependencies.
Create a lower-constraints.txt to be used to enforce the lower bounds
in those tests.
Add openstack-tox-lower-constraints job to the zuul configuration.
See http://lists.openstack.org/pipermail/openstack-dev/2018-March/128352.html
for more details.
Change-Id: I5753b175264c074ff722b47293c65063f0187ffe
Depends-On: https://review.openstack.org/555034
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Fix warnings:
doc/image-building.rst:415:undefined label: deploy_a_registry
(if the link has no caption the label must precede a section header)
Change-Id: I8d921f3b05acf9304ccf41e172926887088b97d7
Bandit was not running in all directories
due missing -r parameter.
Also, this change fix bandit errors.
* Add nosec to subprocess module
* Change /tmp/releases to .releases
* Change /tmp/ to tmp/, tmp/ is not checked
and in unittest is not an issue, simpler that mocking tempfile
and make more complex tests.
Change-Id: I42bafa4707a9a4d1faeb01cb9b5a843f56280deb
Some of the available checks are disabled by default, like:
[H106] Don’t put vim configuration in source files
[H203] Use assertIs(Not)None to check for None
Change-Id: I61ce619eeb37dc05f81015d37afc78a32838448a
At the moment, deploy_aio.sh is called with sudo which results
in the environment being wiped. This means that all Zuul
environment variables are removed and therefore when zuul-cloner
runs to checkout the branch of kolla-ansible, it will always
fallback to master as ZUUL_BRANCH is unset.
This patch removes the global usage of sudo in the tox.ini file
as there is existing usage of sudo in the bash script itself. This
will mean that we will only escalate privileges when needed rather
for the whole script and the environment variables should be passed
on properly resulting in the matching release of kolla-ansible being
checked out.
Closes-Bug: #1673756
Change-Id: I477a843e696be7136c020be6408afea01967879d
This patch add the coverage tool package to test-requirements.txt
which was missing, while kolla support coverage. In addtion to this
tox.ini coverage command is modified to reflect the coverage report
in standard output whenever "tox -e cover" command run for better
representation of coverage report.
Change-Id: I7f77c8d5320a7d180586ce1e8773a4f294846331
Partially-Implements: blueprint coverage-increment-for-kolla
jacky06