Adjust some of the dependencies.
multi_key_dict is not shipped by OpenStack Zuul templates
`build-openstack-docs-pti` or `openstack-cover-jobs` we thus need to
depend on `requirements.txt`.
setuptools v66.0.0 removed support for PEP 440 non-conforming versions.
It provides pkg_resources which we use in PluginVersion.
Tox `whitelist_externals` has been renamed `allowlist_externals`.
Signed-off-by: Antoine Musso <hashar@free.fr>
Change-Id: Ie791c2bb0e7b3784913f45768d2f3db4c66ccae5
stestr 3.0.0 does not support python 2.7 but has been released without
the proper metadata to reflect that. As a result, there is a python2 wheel
stestr-3.0.0-py2-none-any.whl which get picked up.
Blacklist stestr 3.0.0 to fix '--list': no such option error
Drop pypy testing since pypy jobs are always failling.
Signed-off-by: Antoine Musso <hashar@free.fr>
Signed-off-by: Andreas Jaeger <aj@suse.com>
Change-Id: Ia2f7c814f21c78f29ec9024997469625f92bc401
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: I80117242630a1aa6df39b33b0ab66616ab8923a9
Story: #2002586
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: I8146e56453c518f8d8ae822157c1e4931708959a
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: I56890d9f5d258bc27f94c51c369a774b2978c0fc
Adds a new job that tests if change affects jenkins-job-builder
master branch in order to avoid introducing breaking changes
in the most important consumer of the this library.
Also adds an optional tox target named tips which can be used
by developers to perform the same kind of testing. This
mimics the same kind of testing that was already implemented
inside jenkins-job-builder.
Change-Id: I594347c431a881227c5090b41b4ba4ef50e3133f
Signed-off-by: Sorin Sbarnea <ssbarnea@redhat.com>
Switch to use stestr which is maintained as opposed
to testrepository (testr) which became a defunct project.
Change-Id: If53c985b6cf3b4122596f09ec4d0ec4a186688b8
python-jenkins fails to build without the kerberose packages and those
packages are not included in our xenial images. Use bindep to
configure the required minimum set of required packages.
build error:
building 'kerberos' extension
creating build
creating build/temp.linux-x86_64-2.7
creating build/temp.linux-x86_64-2.7/src
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes
-fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong
-Wformat -Werror=format-security -fPIC -I/usr/include/python2.7 -c src/base64.c
-o build/temp.linux-x86_64-2.7/src/base64.o sh: 1: krb5-config: not found
x86_64-linux-gnu-gcc: error: sh:: No such file or directory
x86_64-linux-gnu-gcc: error: 1:: No such file or directory
x86_64-linux-gnu-gcc: error: krb5-config:: No such file or directory
x86_64-linux-gnu-gcc: error: not: No such file or directory
x86_64-linux-gnu-gcc: error: found: No such file or directory
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
----------------------------------------
Failed building wheel for kerberos
Change-Id: Iad6e10ef6ef05e0b5c6db08dbb97b2c3a3e42a30
"Python 3.3 support is being dropped since OpenStack Liberty."
written in following URL.
https://wiki.openstack.org/wiki/Python3
And already the infra team and the oslo team are dropping py33
support from their projects.
Since we rely on oslo for a lot of our work, and depend on infra
for our CI, we should drop py33 support too.
Change-Id: Id129b5c418ad49ea805888309d031ff8a9960be9
Closes-Bug: #1526170
If we run python3 tests before python2 tests the testrepository DB works
fine. If we run python2 first the python3 tests cannot read the
testrepository DB. The simple fix here is to change the order of the tox
env list so that python3 always runs first.
Change-Id: I5118c65f07c0f761e211cd2f186ab11d2f8a3393
Pin mock to < 1.1 as newer versions no longer work on python 2.6.
Remove duplicate unittest2 for python 2.6 test env.
Adding warning to mark python 2.6 support as deprecated and intended to
be removed.
Testtools re-added the requirement for unittest2 so the separate
dependency for python 2.6 created a duplicate error that causes tox
to fail.
Change-Id: Ia79eeeb5d2432cf1025631a1722de5fb1babe2c9
This patch aims to pin pbr>=0.8.2,<2.0 instead of pbr>=0.8.2,<1.0.
To do that, we also need to update test-requirements.txt to pin hacking
to <0.11 (like in current Global OpenStack requirements).
We also need to ignore some hacking rules.
Some distros ship 1.0.1 so it conflicts with the version in
requirements.
Change-Id: I3620c5fe72e49e226f2f5d1e6c36179eb053f424
As per the governance resolution https://review.openstack.org/119875,
projects should have a docs environment in their tox.ini testing
interface. Rename the doc environment to docs.
Change-Id: I19cc2973313db1c1d5816f030cbaee48df1759d7
Six needs to be installed when python-jenkins is installed. By default
test-requirements are only installed when running tests. Six was listed
as a test-requirement so it was not installed when pip installing
python-jenkins. Make six a regular requirement so that it is installed
properly every time.
Change-Id: I2b7cb7e967b20ee0e06fe4c665f08c5932e524f2
Use tox configuration to expose linting and unit testing. Will let us
integrate them with OpenStack continuous integration infrastructure.
* updates .gitignore following the migration from bzr
* get rid of the old Makefile in favor of tox
* remove .pep8 file (that is now a [flake8] section in tox.ini)
* fix a few trivial pep8 errors (comments must start with '# ' and
modulo operator needs surrounding spaces) but ignore 'line too long
(E501)' for now.
* write module requirements in /test-requirements.txt. Discover is
needed for python 2.6.
* change the test command that cames from the Makefile so it works with
python 2.6
Change-Id: If58730d84315c0ea018a3757624d98bf2e1aeb3f
Guillaume DeMengin