sig_cloud/diskimage-builder
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
2275ccb97b
diskimage-builder/tox.ini

46 lines
1.2 KiB
INI
Raw Normal View History

Make it possible for openstack-CI to run tests Per http://wiki.openstack.org/ProjectTestingInterface we enable all of the commands except build_sphinx because we do not have any sphinx documentation as of yet. Includes babel support though there are no properly internationalized strings just yet. Change-Id: Iae6e6b3f9e605106f4575196fa5527d2187255df
2013-01-24 17:42:57 +00:00
[tox]
Switch py34 tests to py35 Py35 is now commonly available on things like -infra test nodes, lets use that instead. Change-Id: I554ec84d709a9937df5ec3c2fa7eab8f158cf64e
2016-12-19 23:21:24 +00:00
envlist = py35,py27,pep8
Updates tox.ini to use new features Reasons: - tox update v1.6 Changes: - tox 1.6 allows us to skip the sdist step, which is slow. - It also allows us to override the install line. In this case, it's important as it allows us to stop getting pre-release software we weren't asking for. Original patch by Monty Taylor, talked about here: http://lists.openstack.org/pipermail/openstack-dev/2013-September/015495.html Change-Id: I7ea029bc75547ccd43566d3329037757d0388112
2013-12-09 14:23:46 +00:00
minversion = 1.6
skipsdist = True
Make it possible for openstack-CI to run tests Per http://wiki.openstack.org/ProjectTestingInterface we enable all of the commands except build_sphinx because we do not have any sphinx documentation as of yet. Includes babel support though there are no properly internationalized strings just yet. Change-Id: Iae6e6b3f9e605106f4575196fa5527d2187255df
2013-01-24 17:42:57 +00:00
[testenv]
Updates tox.ini to use new features Reasons: - tox update v1.6 Changes: - tox 1.6 allows us to skip the sdist step, which is slow. - It also allows us to override the install line. In this case, it's important as it allows us to stop getting pre-release software we weren't asking for. Original patch by Monty Taylor, talked about here: http://lists.openstack.org/pipermail/openstack-dev/2013-September/015495.html Change-Id: I7ea029bc75547ccd43566d3329037757d0388112
2013-12-09 14:23:46 +00:00
usedevelop = True
Add -U to pip install command in tox.ini Ask pip to upgrade packages in the virtualenv so that a long-lived virtualenv is still kept up to date as external dependencies change. Change-Id: I5a57debd5c4bc03e6d00d3801be614d9b895c508
2013-12-11 16:50:02 +00:00
install_command = pip install -U {opts} {packages}
Move Babel and argparse from test-requirements.txt to requirements.txt, to avoid disk-image-create failed without dependencies installed. Change-Id: I110809d298593890b2b050d6da2dcbd036db1ff3
2014-01-16 08:43:21 +00:00
deps= -r{toxinidir}/requirements.txt
-r{toxinidir}/test-requirements.txt
Make it possible for openstack-CI to run tests Per http://wiki.openstack.org/ProjectTestingInterface we enable all of the commands except build_sphinx because we do not have any sphinx documentation as of yet. Includes babel support though there are no properly internationalized strings just yet. Change-Id: Iae6e6b3f9e605106f4575196fa5527d2187255df
2013-01-24 17:42:57 +00:00
commands=
Fix coverage report There's a few things going on here Firstly, we need to install coverage tool in test-requirements Secondly, .testr.conf has to use PYTHON because the coverage report works by resetting PYTHON='coverage run ...' Thirdly, because we call ourselves diskimage-builder but the python module is diskimage_builder that seems to confuse things. We need to use "setup.py test" (note, that is different to "setup.py testr"!) to use the PBR testr wrapper. That exposes a --coverage-package-name argument that calls the coverage tool with the right argument. With this I got a coverage report for our unit tests Change-Id: I9012e18eb7d01bee035140e70afa76c47c27eb01
2017-01-18 04:07:46 +00:00
python setup.py test --slowest --testr-args='{posargs}'
Make it possible for openstack-CI to run tests Per http://wiki.openstack.org/ProjectTestingInterface we enable all of the commands except build_sphinx because we do not have any sphinx documentation as of yet. Includes babel support though there are no properly internationalized strings just yet. Change-Id: Iae6e6b3f9e605106f4575196fa5527d2187255df
2013-01-24 17:42:57 +00:00
[testenv:pep8]
Switch from pep8 to flake8/hacking. Use flake8/hacking, as is standard in other OpenStack projects, but disable new checks -- they will be enabled in later patches. Flake8 catches many useful things http://flake8.readthedocs.org/en/2.0/warnings.html, and hacking enforces the OpenStack Style guidelines, including things like one import per line and alphabetical imports in order to make merging easier. Change-Id: Ib43f7a6790bc17c0b4efdda0a5f891b5a90303c4
2013-06-20 05:32:55 +00:00
commands =
flake8 {posargs}
Add dib-lint script This will provide a place to put checks that catch common errors in elements. To start, this just checks that files starting with a shebang are chmod +x so they can actually be run. Change-Id: I4116a8f38f7bdfc5866764354c459fad8ca18e92
2014-03-20 01:56:27 +00:00
dib-lint
Make it possible for openstack-CI to run tests Per http://wiki.openstack.org/ProjectTestingInterface we enable all of the commands except build_sphinx because we do not have any sphinx documentation as of yet. Includes babel support though there are no properly internationalized strings just yet. Change-Id: Iae6e6b3f9e605106f4575196fa5527d2187255df
2013-01-24 17:42:57 +00:00
Add pylint with indent check This is an initial creation of pylint with a basic indent checker. Small issues corrected. Job added to gate with Ib554a284e92583cc1d6a5c2219b3922852ca4c73 Change-Id: I7e24d8348db3aef79e1395d12692199a1f80161a Co-Authored-By: Andreas Florath <andreas@florath.net>
2017-05-29 06:05:35 +00:00
[testenv:pylint]
setenv = VIRTUAL_ENV={envdir}
deps = pylint
commands = pylint --rcfile pylint.cfg diskimage_builder
Make it possible for openstack-CI to run tests Per http://wiki.openstack.org/ProjectTestingInterface we enable all of the commands except build_sphinx because we do not have any sphinx documentation as of yet. Includes babel support though there are no properly internationalized strings just yet. Change-Id: Iae6e6b3f9e605106f4575196fa5527d2187255df
2013-01-24 17:42:57 +00:00
[testenv:venv]
commands = {posargs}
Add a tox target to run functional tests locally Now 'tox -efunc' can be invoked to run all functional tests in the 'venv' tox environment. Also `tox -efunc element-name` can be used to run function tests for one element (e.g. ironic-agent). Change-Id: Ia685d1b2a7deef2f8b98876ac09792134dd30f2f
2015-09-30 09:55:40 +00:00
[testenv:func]
envdir = {toxworkdir}/venv
commands = {toxinidir}/tests/run_functests.sh {posargs}
Make it possible for openstack-CI to run tests Per http://wiki.openstack.org/ProjectTestingInterface we enable all of the commands except build_sphinx because we do not have any sphinx documentation as of yet. Includes babel support though there are no properly internationalized strings just yet. Change-Id: Iae6e6b3f9e605106f4575196fa5527d2187255df
2013-01-24 17:42:57 +00:00
[testenv:cover]
Fix coverage report There's a few things going on here Firstly, we need to install coverage tool in test-requirements Secondly, .testr.conf has to use PYTHON because the coverage report works by resetting PYTHON='coverage run ...' Thirdly, because we call ourselves diskimage-builder but the python module is diskimage_builder that seems to confuse things. We need to use "setup.py test" (note, that is different to "setup.py testr"!) to use the PBR testr wrapper. That exposes a --coverage-package-name argument that calls the coverage tool with the right argument. With this I got a coverage report for our unit tests Change-Id: I9012e18eb7d01bee035140e70afa76c47c27eb01
2017-01-18 04:07:46 +00:00
# NOTE: this is "setup.py test" (*not* testr) which is a pbr wrapper
# around testr. This understands --coverage-package-name which we
# need due to underscore issues.
commands = python setup.py test --coverage --coverage-package-name diskimage_builder --testr-args='{posargs}'
Make it possible for openstack-CI to run tests Per http://wiki.openstack.org/ProjectTestingInterface we enable all of the commands except build_sphinx because we do not have any sphinx documentation as of yet. Includes babel support though there are no properly internationalized strings just yet. Change-Id: Iae6e6b3f9e605106f4575196fa5527d2187255df
2013-01-24 17:42:57 +00:00
Add `tox -edocs` capability This is much easier to remember than the full commandline - and keeps this project in line with others Change-Id: I2f631c25d8839272941b7c8d4bb571a853422083
2015-02-09 20:58:58 +00:00
[testenv:docs]
commands = python setup.py build_sphinx
Add releasenotes Use reno to start at keeping release notes. Add an initial log. Change-Id: Iba3ebd3b01c15030ac2585dda82e43657e511310
2016-03-14 03:29:28 +00:00
[testenv:releasenotes]
commands = sphinx-build -a -W -E -d releasenotes/build/doctrees -b html releasenotes/source releasenotes/build/html
Switch from pep8 to flake8/hacking. Use flake8/hacking, as is standard in other OpenStack projects, but disable new checks -- they will be enabled in later patches. Flake8 catches many useful things http://flake8.readthedocs.org/en/2.0/warnings.html, and hacking enforces the OpenStack Style guidelines, including things like one import per line and alphabetical imports in order to make merging easier. Change-Id: Ib43f7a6790bc17c0b4efdda0a5f891b5a90303c4
2013-06-20 05:32:55 +00:00
[flake8]
Release 1.25.2 -----BEGIN PGP SIGNATURE----- iQEcBAABAgAGBQJYV1yqAAoJEBty/58O8cX8hLwIAKP66w6MdPN8PDgUOteui/Sx N0UFKJ9yR4GQOAP0NffPLjch5/g0iJLs3eFKOhtGC1LjbDjpVgjX8vW18ib8wBZK GemOZPF3uxg8FROrZF1vpoDy/cHgL1YV10hCnwdjN/r9rb8zOuSabqjW+Dennj2n fZ0SJfa8Owfudn3YxGuOymVb/wMtEloDmVGBEI1Y+h7osELCCDi3OXmwsA8qMsdl cTwbeugBs4PlOVbZUK/JKGuwIHKgPnDYzYu5KpXw77/MdjGT0fo5Tlq5AOBDI2sC 9JOFEBDli4Ro05VwvI58ADMpvvOax+9EvOhLbB1dRPdZl21Iyb6gOdy2PUbFO0c= =aKxq -----END PGP SIGNATURE----- Merge tag '1.25.2' into merge-branch Release 1.25.2 Change-Id: I698bcf2e82117bd81649cd065a7af5cac85990c7
2017-02-01 23:57:40 +00:00
ignore = E125,E126,E127,H202,H803
Semi-automatic doc generation of element dependency Currently there is no description of dependencies in the generated documentation of the elements: therefore a user of an element does not know which other elements are automatically included and e.g. which configuration options are available. In addition there are some copy&pastes of parts of the README.rst scattered thought different Ubuntu and Debian specific elements. This patch adds a semi-automatic generation of dependency information of all elements. Nevertheless these are not automatically included. The author of the element's README.rst can decide if and where the dependency information should appear and can use the descriptor .. element_deps:: for this. This patch adds the dependency information for some Debian and Ubuntu patches - and creates the base for later removing the duplicated parts. A call is added to element_dependencies._find_all_elements() to populate reverse dependencies for Element objects. (This is a reworking of I31d2b6050b6c46fefe37378698e9a330025db430 for the feature/v2 branch) Change-Id: Iebb83916fed71565071246baa550849eef40560b
2017-01-19 21:00:21 +00:00
exclude = .venv,.git,.tox,dist,doc/build,doc/source,*lib/python*,*egg,build,conf.py
Reference in New Issue Copy Permalink