> On Jun 16, 2017, at 5:07 AM, Benedikt Ritter wrote:
>
> Hi,
>
>> Am 15.06.2017 um 15:17 schrieb Rob Tompkins :
>>
>> Hello all,
>>
>> We’ve started an experiment in [text] in regards to using travis-ci to build
>> inside containers (specifically ibmjava at this point). It seems that it’s a
> Am 16.06.2017 um 11:07 schrieb Benedikt Ritter :
>
> Hi,
>
>> Am 15.06.2017 um 15:17 schrieb Rob Tompkins :
>>
>> Hello all,
>>
>> We’ve started an experiment in [text] in regards to using travis-ci to build
>> inside containers (specifically ibmjava at this point). It seems that it’s a
>>
Hi,
> Am 15.06.2017 um 15:17 schrieb Rob Tompkins :
>
> Hello all,
>
> We’ve started an experiment in [text] in regards to using travis-ci to build
> inside containers (specifically ibmjava at this point). It seems that it’s a
> non-standard practice with regards to travis-ci.
>
> I suppose m
Hello,
Using docker would be much better and flexible solution (in case we know
how to use it). I would also recommend to look at how jococo handling
multiple JDK in their project[1]. If it's convincing we might want to scrap
our .travis.yml altogether and go with that.
[1] https://github.com/j
Hello all,
We’ve started an experiment in [text] in regards to using travis-ci to build
inside containers (specifically ibmjava at this point). It seems that it’s a
non-standard practice with regards to travis-ci.
I suppose my question is: is anyone familiar with using travis-ci and
specifyi
