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/jacoco/jacoco/blob/master/.travis.yml Regards, Amey On Jun 15, 2017 6:47 PM, "Rob Tompkins" <chtom...@gmail.com> wrote: > 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 > specifying custom containers in which to run your build? Give the > .travis.yml a look in commons-text (https://github.com/apache/ > commons-text/blob/master/.travis.yml) and let me know what you think. > Clearly we’re trying to use ibmjava to build the project, but it’s > definitely running that build on each of the 3 environments that we’re > running in and exits with a 0 from the docker run command regardless of if > the build fails. > > Any thoughts? > > Cheers, > -Rob >
