15 Jun
2016
15 Jun
'16
2:16 a.m.
Rene Rivera
As part of continued efforts to move testing to CI, to facilitate release management, and to provide more information to authors I've now implemented some testing changes:
1. Most libraries are now tested automatically if they have a usable test directory.
How will this interact with libraries that already have their own CI setup? Is your CI triggered whenever a submodule is synced to boostorg/boost? If so, there's going to be quite a bit of redundant testing being done, and since all of boostorg is sharing the same Travis resources (I think), that could quickly become a problem. Is this a valid concern? Louis