Geometry Boost List: Re: [geometry] Setting up Travis CI for Boost.Geometry

Subject: Re: [geometry] Setting up Travis CI for Boost.Geometry
From: Adam Wulkiewicz (adam.wulkiewicz_at_[hidden])
Date: 2014-11-10 13:36:24

Adam Wulkiewicz wrote:
> Mateusz Loskot wrote:
>> On 10 November 2014 16:31, Adam Wulkiewicz 
>> <adam.wulkiewicz_at_[hidden]> wrote:
>>> AFIO has many icons in their README but indeed there is only one from
>>> Travis.
>>> https://github.com/BoostGSoC13/boost.afio
>> Yes, Travis status image is generated per branch build:
>> https://api.travis-ci.org/mloskot/geometry.svg?branch=master
>> https://api.travis-ci.org/mloskot/geometry.svg?branch=develop
>> ,,,
>> No customisations.
>>
>>> What if we made some dummy branches, each one testing one part of the
>>> library?
>> How would that differ from telling b2 what to build?
>>
>> b2 target1 target2 target3
>>
>> ...but not target4.
>
> Since AFAIU Travis generates a result image per branch, the only way 
> to generate multiple images (for various parts of the lib) is to run 
> the tests for various (dummy) branches each testing a part. Those 
> resulting images may be then inserted into one README. Or am I missing 
> something?
>

Or maybe better, to not create dummy branches in the original repo we 
could have a fork designated for testing with all of the additional 
branches and configuration files, etc.
We should just figure out how to automatically update it after 
develop/master was changed, or at least how to update it periodically.

> Regards,
> Adam