On 20 September 2017 at 18:52, John Maddock via Boost
This isn't feasible as CI jobs have a time limit of 49 minutes on Travis, which is sometimes insufficient for testing even a single library.
I think this is the problem with this approach: any non-trivial library will quickly run out of time on the CI servers, some of which are rather slow. Certainly Math and Multiprecision libraries had to be split into multiple jobs to get through CI testing. I'm sure there are many others with similar issues.
There is another related issue: unless everyone is completely disciplined about putting [CI skip] in commit messages for documentation only commits, this is going to trigger a lot of needless jobs?
FYI, AppVeyor allows to configure commit filters to only build if C++ files or Jamfiles are touched, for instance. https://www.appveyor.com/docs/how-to/filtering-commits/ Best regards, -- Mateusz Loskot, http://mateusz.loskot.net