tox-travis
tox-travis copied to clipboard
tox-dev
Seamless integration of tox into Travis CI
eg https://github.com/abusalimov/pytest-travis-fold spec here https://blog.travis-ci.com/2013-05-22-improving-build-visibility-log-folds/
Travis supports development version like `3.8-dev` but it is unclear if a config like ``` [travis] python = 3.8: py38,coveralls,custom ``` should run all envs for the Travis python 3.8-dev...
``` [testenv] deps = pytest u: pylint commands = u: pylint -E . s: pytest \ -c tox.ini \ --junit-prefix={envname} {posargs} ``` Breaks ``` ERROR: InvocationError for command could not...
Having both tox-factor and tox-travis living together, for instance, causes one to override the other. Since they both read the full list of environments directly from the config, whichever one...
https://github.com/pglass/tox-pip-version/issues/14 is considering using the alpha Travis Windows, and is probably a good candidate for using tox-travis . The Windows VMs do start up quite quickly, making it a viable...
https://docs.travis-ci.com/user/using-workspaces/ - beta feature, very useful for coverage merging and also for doing a publish phase "after" all other jobs.
This might be related to #58 but I'm not sure. I'd like to integrate [tox-docker](https://github.com/tox-dev/tox-docker) into [my project](https://github.com/stephenfin/patchwork/tree/tox-docker-integration). I currently have `[tox] envlist` like so: envlist = pep8,docs,py{27,34}-django111,py{35,36}-django{111,20,21,22} I want...
Rather foolish now I think about it, I was expecting the following to ```ini [travis:env] TRAVIS_LANGUAGE = swift,objectivec,objective_c,objective-c: py36-swift-noskip ``` to be expanded to ``` [travis:env] TRAVIS_LANGUAGE = swift: py36-swift-noskip...
It might be useful to document in the env detection section that users can debug/test tox-travis's envlist matching by setting the appropriate CI environment variables. e.g., `TRAVIS=yes TRAVIS_PYTHON_VERSION=3.7 tox -l`...
