Excluding junos, which is still its own thing and not currently a problem, we have 28 integration jobs running on netcommon commits, which is each of the following:

• eos-httpapi
• eos-paramiko
• eos-libssh
• ios-paramiko
• ios-libssh
• vyos-paramiko
• vyos-libssh

Repeated for each of stable-29, stable-211, stable-212, and devel.

These jobs are also running on their respective collections, and so there is a certain amount of overlap of testing. To reduce this, I have identified four ways we could allocate tests to collections:

1. Test ansible version by collection (e.g. eos-stable-2.9, ios-stable-2.11, vyos-stable-2.12, and also still testing devel for every collection):
   • eos-httpapi-stable-2.9
   • eos-httpapi-devel
   • eos-libssh-stable-2.9
   • eos-libssh-devel
   • eos-paramiko-stable-2.9
   • eos-paramiko-devel
   • ios-libssh-stable-2.11
   • ios-libssh-devel
   • ios-paramiko-stable-2.11
   • ios-paramiko-devel
   • vyos-libssh-stable-2.12
   • vyos-libssh-devel
   • vyos-paramiko-stable-2.12
   • vyos-paramiko-devel
2. Test connection type by collection (e.g. eos-httpapi, ios-libssh, vyos-paramiko):
   • eos-httpapi-stable-2.9
   • eos-httpapi-stable-2.11
   • eos-httpapi-stable-2.12
   • eos-httpapi-devel
   • ios-libssh-stable-2.9
   • ios-libssh-stable-2.11
   • ios-libssh-stable-2.12
   • ios-libssh-devel
   • vyos-paramiko-stable-2.9
   • vyos-paramiko-stable-2.11
   • vyos-paramiko-stable-2.12
   • vyos-paramiko-devel
3. We could also combine them to reduce the total amount of integration tests to 6:
   • eos-httpapi-stable-2.9
   • eos-httpapi-devel
   • ios-libssh-stable-2.11
   • ios-libssh-devel
   • vyos-paramiko-stable-2.12
   • vyos-paramiko-devel
4. potentially also picking a different connection to test between the devel and stable tests, e.g.:
   • eos-libssh-stable-2.9
   • eos-httpapi-devel
   • ios-paramiko-stable-2.11
   • ios-libssh-devel
   • vyos-libssh-stable-2.12
   • vyos-paramiko-devel

As mentioned above, this ignores the junos tests for not being network-ee tests and not having as many failures. We could however easily extend any of these lists to have junos cover the netconf connection and/or ansible version 2.10 cases as it is the only platform in either of those configurations