I'm looking at adding support for tox to all of the roles that don't
currently use tox. For example, here is diff of .travis.yml from kdump:
script:
- - molecule --version
- - ansible --version
- - molecule lint
- - molecule syntax
- - molecule test
+ - ./.travis/runtox
and here is the relevant section from tox:
[tox]
envlist =
black, pylint, flake8,
py{26,27,36,37,38},
custom
molecule is not in this list. Should we add molecule to this list?
Seems like we should, or tox conversion will regress travis CI behavior.
we use a tox plugin in the template that makes it use a different set of tests in Travis:
The envlist at the start is meant for environments that are run by default by the user. Since molecule requires special configuration to be able to run docker, it does not make sense to add it there IMHO. If wanted, developers can still run it with "tox -e molecule".
Kind regards
Till
-- Till Maas
He/His/Him
Associate Manager, Software Engineering
NetworkManager, Nmstate, Ansible RHEL Networking System Role
Red Hat GmbH,
http://www.de.redhat.com/, Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Laurie Krebs, Michael O'Neill, Thomas Savage