openstack/requirements
Code Issues Proposed changes
c20eb489fa
requirements/tox.ini

77 lines
2.1 KiB
INI
Raw Normal View History

one global-requirements.txt to rule them all ... and in the darkness bind them. This moves the contents of requirements.txt and test-requirements.txt to a single file, global-requirements.txt. This means that regardless of whether a requirement is in either file it will get checked. This massively simplifies the checking and upgrading of req and test-req files. This also adds in a unit testing framework for the update.py script to ensure it does what we think it does. This is accomplished by making a fake tree with a set of req and test-req files, running update.py, and ensuring the updates were made that we expected. It includes testing for the oslo url case, as well as test-requires. Change-Id: Ib9b86ade4cb8317509e218aec31f32e5d08f4035
2013-07-30 14:35:34 -04:00
[tox]
Have tox install via setup.py develop tox 1.6 was released, which means that we can now take advantage of the feature we added to it - which is using setup.py develop to install the code into the virtualenv. The logic was taken from run_tests.sh - so the performance issues around using tox vs. using install_venv should now be gone. Additionally, override the tox pip install command to avoid using the "--pre" option which is the default in tox. "--pre" means "Include pre-release and development versions." By default, pip will only install stable versions of software, and that is the behavior we want. Change-Id: I2af4dc6ab460fd8a368b22e3ffbde9467c23f774
2014-01-14 20:13:39 +08:00
minversion = 1.6
skipsdist = True
Check for missing run-time requirements This change creates a new tox environment that *only* installs openstack_requirements and then verifies that each of the console scripts has all of the modules that it imports. This will need to be added to our gate RSN Change-Id: Ibc37593afcc4d9f820cb88168e1aa15e773b2087
2016-06-24 11:36:24 +10:00
envlist = validate,py27,pep8,pip-install
one global-requirements.txt to rule them all ... and in the darkness bind them. This moves the contents of requirements.txt and test-requirements.txt to a single file, global-requirements.txt. This means that regardless of whether a requirement is in either file it will get checked. This massively simplifies the checking and upgrading of req and test-req files. This also adds in a unit testing framework for the update.py script to ensure it does what we think it does. This is accomplished by making a fake tree with a set of req and test-req files, running update.py, and ensuring the updates were made that we expected. It includes testing for the oslo url case, as well as test-requires. Change-Id: Ib9b86ade4cb8317509e218aec31f32e5d08f4035
2013-07-30 14:35:34 -04:00
[testenv]
Check for missing run-time requirements This change creates a new tox environment that *only* installs openstack_requirements and then verifies that each of the console scripts has all of the modules that it imports. This will need to be added to our gate RSN Change-Id: Ibc37593afcc4d9f820cb88168e1aa15e773b2087
2016-06-24 11:36:24 +10:00
basepython = python2.7
Have tox install via setup.py develop tox 1.6 was released, which means that we can now take advantage of the feature we added to it - which is using setup.py develop to install the code into the virtualenv. The logic was taken from run_tests.sh - so the performance issues around using tox vs. using install_venv should now be gone. Additionally, override the tox pip install command to avoid using the "--pre" option which is the default in tox. "--pre" means "Include pre-release and development versions." By default, pip will only install stable versions of software, and that is the behavior we want. Change-Id: I2af4dc6ab460fd8a368b22e3ffbde9467c23f774
2014-01-14 20:13:39 +08:00
usedevelop = True
install_command = pip install -U {opts} {packages}
one global-requirements.txt to rule them all ... and in the darkness bind them. This moves the contents of requirements.txt and test-requirements.txt to a single file, global-requirements.txt. This means that regardless of whether a requirement is in either file it will get checked. This massively simplifies the checking and upgrading of req and test-req files. This also adds in a unit testing framework for the update.py script to ensure it does what we think it does. This is accomplished by making a fake tree with a set of req and test-req files, running update.py, and ensuring the updates were made that we expected. It includes testing for the oslo url case, as well as test-requires. Change-Id: Ib9b86ade4cb8317509e218aec31f32e5d08f4035
2013-07-30 14:35:34 -04:00
setenv = VIRTUAL_ENV={envdir}
tox: Install packages from requirements.txt as well Change-Id: I75e3086862b83c8eeba79e984d3ac5b7335cd832
2016-12-26 13:51:55 +09:00
deps = -r{toxinidir}/requirements.txt
-r{toxinidir}/test-requirements.txt
one global-requirements.txt to rule them all ... and in the darkness bind them. This moves the contents of requirements.txt and test-requirements.txt to a single file, global-requirements.txt. This means that regardless of whether a requirement is in either file it will get checked. This massively simplifies the checking and upgrading of req and test-req files. This also adds in a unit testing framework for the update.py script to ensure it does what we think it does. This is accomplished by making a fake tree with a set of req and test-req files, running update.py, and ensuring the updates were made that we expected. It includes testing for the oslo url case, as well as test-requires. Change-Id: Ib9b86ade4cb8317509e218aec31f32e5d08f4035
2013-07-30 14:35:34 -04:00
commands =
python setup.py testr --slowest --testr-args='{posargs}'
Add pep8 checks Change-Id: Id36116a8a55cf5205634a75c8cc414e96145872a
2013-08-02 13:56:32 -04:00
Add a copy of the check-with-upper-constraints as a shorter name Due to the rename of the job adding the -ubuntu-xenial suffix, we have exceeded the path limit and can no longer run inside the tox environment. shortening to a shorter check name (and renaming the job) should fix this. Change-Id: I0927ae81148d15256bd4dfe2a5e48b1819bbe2af
2016-09-28 17:47:27 +02:00
[testenv:py27-check-uc]
use the constraints list when installing the constraints list Some of the dependencies may not be constrained on their own (pbr) so use the constraints list to enforce the constraints. Change-Id: I3ae5835d1b1b8f75608d7bb110732f9be233b13f Signed-off-by: Doug Hellmann <doug@doughellmann.com>
2017-03-17 10:57:58 -04:00
install_command = pip install -U {opts} -c {toxinidir}/upper-constraints.txt {packages}
Add a copy of the check-with-upper-constraints as a shorter name Due to the rename of the job adding the -ubuntu-xenial suffix, we have exceeded the path limit and can no longer run inside the tox environment. shortening to a shorter check name (and renaming the job) should fix this. Change-Id: I0927ae81148d15256bd4dfe2a5e48b1819bbe2af
2016-09-28 17:47:27 +02:00
deps = -r{toxinidir}/upper-constraints.txt
Fixes for check-uc jenkins job Implement XFAIL handling for ignoring known problems so that we can make the job voting until the remaining issues are sorted out. Change-Id: Ia2cf2c440a72e6365a9ff08086704dc535bbc072
2016-09-29 08:56:54 +02:00
commands = check-conflicts {toxinidir}/upper-constraints.txt {toxinidir}/upper-constraints-xfails.txt
Add python35 check-uc job Change-Id: Ie5d0cf462d7144c25564257d25303d56b810ac24
2017-09-11 13:29:22 -06:00
[testenv:py35-check-uc]
basepython = python3.5
install_command = pip install -U {opts} -c {toxinidir}/upper-constraints.txt {packages}
deps = -r{toxinidir}/upper-constraints.txt
commands = check-conflicts {toxinidir}/upper-constraints.txt {toxinidir}/upper-constraints-xfails.txt
New tox target just for u-c sanity check A simple check to see if all the things specified in upper-constraints.txt can be installed in one shot. Change-Id: Icf6fc2bd53af9dbeec614e0677b81fca55c440ea
2016-05-12 09:37:39 -04:00
Add convenience tox environments Add a venv tox environment like we use in other projects to build a virtualenv and run commands. Add an 'update' environment to run the command for updating the requirements in another project. Add a 'generate' environment to run the command for generating constraints. Change-Id: Ib99fb4da6f62afd31339fa698c8f0e50ce817128
2015-06-22 19:06:23 +00:00
[testenv:venv]
commands = {posargs}
[testenv:update]
commands = update-requirements {posargs}
[testenv:generate]
commands = generate-constraints {posargs}
Move data validation out of the unit tests and strengthen Having the data validation happening inside the unit tests makes understanding requirement update failures confusing because the output is hard to read and does not explain what the error actually is. Move the checks to their own command and set up a tox env to run it. A separate patch in project-config will add a new job for the repository. Address the dedent comment from https://review.openstack.org/#/c/204181/3/openstack_requirements/tests/test_requirement.py,cm Add a test to ensure that all items in global-requirements.txt are also listed in either upper-constraints.txt or blacklist.txt. Ignore a few items that we don't know how to constrain yet. Add a test to ensure that items in blacklist.txt are not in upper-constraints.txt. Change-Id: Icb717b0f36afb6ea29f50bc6935917dddf47fd4c
2015-07-23 20:43:32 +00:00
[testenv:validate]
commands = validate-constraints {toxinidir}/global-requirements.txt {toxinidir}/upper-constraints.txt {toxinidir}/blacklist.txt
add a validation command to ensure projects use check-requirements Add a command and tox environment to let us define a job to ensure that all repos in projects.txt have the check-requirements job defined. Two projects are missing the job now, so this patch depends on the patch to add those jobs. Change-Id: I61658a7265a77e72401978dda558f41b28a81d92 Depends-On: I81e1c70257e28583e776171580d75341e620bf8d Signed-off-by: Doug Hellmann <doug@doughellmann.com>
2016-05-12 16:15:46 -04:00
[testenv:validate-projects]
commands = validate-projects {toxinidir}/projects.txt
Add pep8 checks Change-Id: Id36116a8a55cf5205634a75c8cc414e96145872a
2013-08-02 13:56:32 -04:00
[testenv:pep8]
commands = flake8
Add a bashate tox environment and address errors Add a bashate environment for checking shell code quality. Exclude bashate warnings: E006: Line too long: E010: The "do" should be on same line as for In my opinion the places that trip these do not impact code readability Change-Id: Iab0a34542c3938f127515291eca8f027f3accaa0
2017-09-28 12:07:09 +10:00
[testenv:bashate]
whitelist_externals = bash
# E006: Line too long:
# E010: The "do" should be on same line as for
commands = bash -c "find {toxinidir}/tools \
-type f \
-name \*.sh \
-print0 | xargs -0 bashate -v -iE006,E010"
Add simple doc publisher target Add a simple doc publisher target that just includes the existing README. Some of the infra jobs that fail requirements try to point you to the requirements documentation; currently this is given as a raw RST link to the web-view of the git tree. It would be nicer to publish this as formatted HTML like all the other docs. Change-Id: I56b60a950c64880dd551d11e1997cd5ecbae283c
2015-09-29 12:15:25 +10:00
[testenv:docs]
commands = python setup.py build_sphinx
Check for missing run-time requirements This change creates a new tox environment that *only* installs openstack_requirements and then verifies that each of the console scripts has all of the modules that it imports. This will need to be added to our gate RSN Change-Id: Ibc37593afcc4d9f820cb88168e1aa15e773b2087
2016-06-24 11:36:24 +10:00
[testenv:pip-install]
recreate = True
deps = .
install_command = pip install {opts} {packages}
commands = python {toxinidir}/tools/check-install.py
[testenv:py34]
basepython = python3.4
[testenv:py35]
basepython = python3.5
Babel Integration tests With Babel 2.2 and then with Babel 2.3.2 and 2.3.3 releases, the OpenStack infra scripts broke and uncovered bugs in the upstream Babel release. The infra scripts run in post and periodic queues, so failures here are not directly visible. With Babel 2.3.x invalid strings were send to the translation server, and we had to recover old content to fix this. Let's add some Babel integration tests that can be run whenever the upper-constraints file changes so that any new Babel release will be at least minimally tested. The shell script babel-test.sh runs a simple extraction of strings to translate from a simple input file. It uses the same commands that the infra scripts run and handles the two different cases of extraction of the normal strings and extraction of the non-standard log-level strings. The script then compares the new content with previously created good content. Once this change is in, we will run this test whenever upper-constraints.txt file changes. Needed-By: I15fa6a706323615d6072d8acaa859fea9bf35883 Change-Id: Iab7844ba748ecd84ec07ad4280b2317bd626fe9a
2016-04-24 10:40:47 +02:00
[testenv:babel]
# Use the local upper-constraints.txt file
deps = Babel
install_command = pip install -c upper-constraints.txt {opts} {packages}
Fix babel test Add missing {toxinidir} to path, currently the test fails with: could not find executable 'tools/babel-test.sh' Change-Id: I71420066c6d293cd9b117de7f84ae124d26f7d34
2016-05-04 18:56:14 +02:00
commands = {toxinidir}/tools/babel-test.sh
Babel Integration tests With Babel 2.2 and then with Babel 2.3.2 and 2.3.3 releases, the OpenStack infra scripts broke and uncovered bugs in the upstream Babel release. The infra scripts run in post and periodic queues, so failures here are not directly visible. With Babel 2.3.x invalid strings were send to the translation server, and we had to recover old content to fix this. Let's add some Babel integration tests that can be run whenever the upper-constraints file changes so that any new Babel release will be at least minimally tested. The shell script babel-test.sh runs a simple extraction of strings to translate from a simple input file. It uses the same commands that the infra scripts run and handles the two different cases of extraction of the normal strings and extraction of the non-standard log-level strings. The script then compares the new content with previously created good content. Once this change is in, we will run this test whenever upper-constraints.txt file changes. Needed-By: I15fa6a706323615d6072d8acaa859fea9bf35883 Change-Id: Iab7844ba748ecd84ec07ad4280b2317bd626fe9a
2016-04-24 10:40:47 +02:00
Add pep8 checks Change-Id: Id36116a8a55cf5205634a75c8cc414e96145872a
2013-08-02 13:56:32 -04:00
[flake8]
exclude = .venv,.git,.tox,dist,doc,*egg,build
Copy Permalink