Re: [all/travis-ci] Regarding potential Travis-CI solutions

Closed PR. On Mon, Aug 7, 2017 at 2:12 AM, Amey Jadiye wrote: > looking at inclination of community I will be closing the PR without > expecting merge after a week by 14th August 2017 unless someone see it's > useful. > > Reference will be there in closed PR list on github

Re: [all/travis-ci] Regarding potential Travis-CI solutions

looking at inclination of community I will be closing the PR without expecting merge after a week by 14th August 2017 unless someone see it's useful. Reference will be there in closed PR list on github so if someone need it in future it will be there. Regards, Amey On Fri, Aug 4, 2017, 3:02 AM

Re: [all/travis-ci] Regarding potential Travis-CI solutions

[I don't know anything about Travis, so this may be a non-starter.] The ASF Jenkins jobs can be set up with environment variables that point to different JDKs. If there is something similar for Travis, then the script could use those. It would then be up to the Travis maintainers to ensure that

Re: [all/travis-ci] Regarding potential Travis-CI solutions

Hi, Yes we are giving up the simplicity of travis but I see some advantages over it, all of them are listed in my previous mail, let me try to put them again. 1. Travis provides very limited JDK at this point [1] and travis builds can become more flexible and we will have more control over the

Re: [all/travis-ci] Regarding potential Travis-CI solutions

I agree with Pascal. It's better to use Travis build in stuff. When IBM Jdk really become available, that would be quite nice, because that tends to cause failures. Regarding EA builds, I think it's good enough to test releases against them. Since EA builds may have regressions, this could lead to

Re: [all/travis-ci] Regarding potential Travis-CI solutions

Hello everybody, let me add some detail to what I mean by hard to maintain. The scripts contains links to specific jdk versions: http://download.java.net/java/jdk9/archive/178/binaries/jdk-9+178_linux-x64_bin.tar.gz

[all/travis-ci] Regarding potential Travis-CI solutions

Hello all, We have an open pull request from Amey (https://github.com/apache/commons-text/pull/61 ) proposing a fairly complicated but quite nice travis-ci build solution (taken from the jacoco project) that accommodates building on JDK7, JDK8,