[Pulp-dev] [CI] [Installer] We should not test ansible-pulp against multiple versions of Python on the mgmt node
mikedep333 at redhat.com
Fri Feb 14 15:45:58 UTC 2020
Hi CI & Installer teams,
I talked with James Tanner (who works on Ansible Core), and his advice was
that we should not bother to test our ansible-pulp (a collection of roles)
against multiple versions of Python on the management node (the Travis
We still need to test a variety of Linux distros (with their bundled python
versions) for managed nodes, which we do (molecule creates containers for
This is because we meet the following criteria:
1. We do not write any python code, "action plugins" that run on the
management node (and none for the managed node either, like role-bundled
2. We use few "action plugins" on the management node (the "package" module
includes one to decide whether to use dnf/yum/apt/etc), and those we do use
are probably all well tested by Ansible's first-party CI. It's difficult to
enumerate those we use, and not worth enumerating. It's not like we use
community-supported action plugins.
If there are no objections, I will create a low redmine tasks to make our
Travis PR approach (static test case on Python 2.7 only, upgrade test case
on 3.6 only, dynamic test case on 3.7 only) replace our complete 3x3 matrix
approach of cron jobs.
If in the future we do not test every version of Python on the management
node, we should not be overly concerned either.
He / Him / His
Service Reliability Engineer, Pulp
Red Hat <https://www.redhat.com/>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pulp-dev