Boost logo

Boost :

Subject: Re: [boost] Boost summer of formal reviews
From: Niall Douglas (s_sourceforge_at_[hidden])
Date: 2014-03-11 20:08:33

On 11 Mar 2014 at 23:51, Borislav Stanimirov wrote:

> > with an auto-reject if it's not above 75%. Travis CI +
> At first that got me really excited, but as I found out after a short
> research, even Boost.AFIO's .travis.yml indicates that getting a Boost
> library to build with Travis CI is very hard, if at all reasonable.

You surprise me. Simply clone AFIO's travis.yml and adjust as fit,
it's only Unix shell scripting. Note most of the tests are commented
out because I have Jenkins CI doing all the testing.

> I may be willing to add CI to my library, but it doesn't seem like
> Travis would be the way to go about that

You may need to reorg your Boost testing to compile all your tests
into a single, monolithic test binary which runs all the tests at
once (you can see how AFIO did this, Paul came up with a cunning
portable batch/shell script). You can then feed said binary into
valgrind, have clang do a ThreadSanitize, and of course run it

Travis gives you 20 mins for download, install, build and test
duration (longer if you're printing output), so make sure all your
tests finish (including when run in valgrind) before then. Tip:
precompiled headers are useful here, look into AFIO's --fast-build
build switch.

Travis isn't perfect, and only CI's on Linux, but it is very good.
And it's free.


Currently unemployed and looking for work in Ireland.
Work Portfolio:

Boost list run by bdawes at, gregod at, cpdaniel at, john at