Re: [RFC] Refactor autoconf options and build scripts

[Jean-Marie Lemetayer <jeanmarie.lemetayer@gmail.com>]

Well, here is the first serial build result:
https://travis-ci.org/jmlemetayer/crosstool-ng/builds/80435130

Conclusion, doing serial build is space consuming ... :-) So we have
to add some `rm` between each builds.

I also tried to do parallel builds:
https://travis-ci.org/jmlemetayer/crosstool-ng/builds/80447510

Travis CI handle this very well and as you can see it is easy to see
which sample is good and which one is not. It is also more easy to
read the log on failure.

Personally, I think parallel builds could be a good option.

Regards,
JML

2015-09-15 16:39 GMT+02:00 Trevor Woerner <twoerner@gmail.com>:
> On 09/15/15 10:21, Jean-Marie Lemetayer wrote:
>> To continue the Jasmin work about Travis-CI, I have copy paste the
>> Jasmin `.travis.yml` on my fork and add a script line to build all
>> samples this way:
>>
>>     for SAMPLE in $(./ct-ng list-samples 2>/dev/null | sed -n
>> 's/^\[...\] *\(.*\)$/\1/p'); do ./ct-ng $SAMPLE; ./ct-ng build; done
>>
>> It seems to be working for now: https://travis-ci.org/jmlemetayer/crosstool-ng
>>
>> But going further into the Travis-CI documentation I see that the
>> build timeouts after 50 minutes:
>> http://docs.travis-ci.com/user/customizing-the-build/#Build-Timeouts
>>
>> So it seems not to be the good strategy as building all samples
>> serially will take more than 50 minutes. But we could run parallel
>> builds using matrix build:
>> http://docs.travis-ci.com/user/customizing-the-build/#Build-Matrix
>>
>> The only difference is that we can't run build dynamically (using
>> `list-samples`) and we have to say which samples we want to build for
>> the continuous integration.
>
> Maybe you could rework your "for SAMPLE in..." script to run each sample
> in a subprocess then wait for the results?
>
> http://stackoverflow.com/questions/356100/how-to-wait-in-bash-for-several-subprocesses-to-finish-and-return-exit-code-0
>
> That way the number of sample is still generated dynamically, the
> results can be collected to show if any fail (or if they all succeed),
> and the whole build (hopefully) still takes less than 50 minutes?

--
For unsubscribe information see http://sourceware.org/lists.html#faq