the build matrix can't be extended to dependencies unfortunately. You have one set of dependencies for all builds.
could you not 'fake it' by pointing the 'break?' build to random/non existant include directories so that the configure stage cant find them?
The problem is you can't run multiple test sets. You have one .travis.yml file it lets you specify one set of dependencies, one configure/make, and one set of test scripts. If you were allowed multiple .travis.yml files it'd be fine, but you're not.
and now LDAP with dynamic-clients :)
yes...well, point made! ;-)
Yeah, all that code needs consolidating so there's only one code path for creating new clients. Or tests... tests would be nice.
If they want to use RADSEC they have two options, use a gateway, or upgrade.
..and to stimulate a reply.. I'd say its currently easier to configure a 2.x system to use a gateway/proxy than it is to upgrade from 2.x to 3 to use the native capability 8-)
Probably. Oh well. Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS Development Team