OSDir


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Lighter build matrix on a language specific fork.


I must do something wrong then because it builds them all, all the time 🤷‍♂️.

Not a big deal, it’s only about 10 jobs, and i really only care about the r job and the only doing the 🐀 analysis. 

Commenting out may not be very practical as the plan is to submit small pull requests, so it’s almost guaranteed i’ll forget to uncomment about 50% of the time. 

> Le 6 sept. 2018 à 14:48, Antoine Pitrou <antoine@xxxxxxxxxx> a écrit :
> 
> 
> Our CI harness will already fast-exit in jobs that are not affected by
> the current changes (if you change only the R directory, C++ jobs will
> exit early).
> 
> If you want it to be even faster, your best bet is to temporarily
> comment out job entries in .travis.yml.
> 
> Regards
> 
> Antoine.
> 
> 
>> Le 06/09/2018 à 14:26, Romain François a écrit :
>> Hello, 
>> 
>> Is there a way to have a lighter build matrix on travis, perhaps based on the branch name, for example when working on the r bindings and not touching anything else, having only the r job to be triggered would make it faster for travis. 
>> 
>> For example when working on r features i would typically start the branch name with « r-»
>> 
>> Romain
>>