Hello All, We need community opinion here as this change request can improve / affect many other components in near future.
I have proposed the change in PR https://github.com/apache/commons-text/pull/61 so the travis builds can become more flexible and we will have more control over the different flavours, versions and vendors of jdk we wants to use via travis build process. I personally think that travis is very slow providing the different versions of jdk ATM ... PR contains two files one is generic .travis.sh which is generalised and .travis.yml which is commons-text specific. Some may feel script is complex [I don't think it is complex might be because I worked on it ;-)] but once it become mature it will be pretty stable and need no change, depending on components requirements each can decide which jdk/vendor/version they want in their .travis.yml For the sake of start and demo I have added wide verity of jdk in build like java7, java8, java9, earyl access, eclipse compiler option, oraclejdk, openjdk, ibm jdk etc.... and that can me made configurable easily so no much maintenance needed once we are done with it, I'm expecting improvements / suggestions from you guys to improve it more for the need of commons. Other thing I'm proposing is to have this script as .travis.parent.sh and we can keep it somewhere centralised http location and wget it and execute from .travis.sh so core logic will have to maintain at single place, change will be only in respective .travis.yml. what do you guys think ? Regards, Amey On Fri, Jul 28, 2017 at 6:02 PM, Amey Jadiye <ameyjad...@gmail.com> wrote: > Thanks, I'm taking Commons Text as my test guineapig for jacoco style > implementation , once confident in implementation we can move it to other > components. > > Regards, > Amey > > On Jul 28, 2017 5:39 PM, "Rob Tompkins" <chtom...@gmail.com> wrote: > >> >> > On Jul 27, 2017, at 4:10 PM, Amey Jadiye <ameyjad...@gmail.com> wrote: >> > >> > Hi Rob, >> > >> > If this is still pending I would like to pickup this task. If docker is >> not >> > much helpful OR we need to wait for it I think we should try what >> jacoco >> > did. what do you think ? >> >> Sure. That makes sense to me, especially since the Travis folks say that >> they’ve got on the backlog to install the IBM JDKs on their build >> environments. >> >> > >> > Is it mandatory to use official java images ?Else I am also thinking to >> > create my own ibmjdk8 image on top of given by IBM and have some tools >> and >> > scrips ready in that so on fail it should return -1. >> >> I contributed to the official maven docker image to add the ibm jdk, but >> I”m not sure how the build works out there. So I’m not sure it’s in docker >> hub yet. >> >> > >> > Not sure how much travis-ci be helpful here since I saw Pascal removed >> > oraclejdk7 from .travis configuration because its not available. I'm not >> > keeping much hopes on Travis at this point as their provision on >> different >> > jdk images seems very slow to me . >> >> I think there was some flavour of issue with Java7 in that the image >> wasn’t loading properly. It could be worth trying the jacoco approach to >> see if that works. >> >> -Rob >> >> > >> > Regards, >> > Amey >> > >> > On Sat, Jul 1, 2017, 6:43 PM Rob Tompkins <chtom...@gmail.com> wrote: >> > >> >> Hello all, >> >> >> >> Pardon my disappearance for the last week or so. My day job has been a >> >> little over consuming (c’est la vie). Regardless, I’ve been looking at >> how >> >> we can use the current appetite in the travis-ci community to push >> them to >> >> install ibmjava8 and ibmjava9 in this working thread: >> >> https://github.com/travis-ci/travis-ci/issues/2682 < >> >> https://github.com/travis-ci/travis-ci/issues/2682>. Hopefully we can >> >> gain some traction there. >> >> >> >> Regardless, they seem to have far more idk’s installed in their build >> >> environment than documented >> >> https://github.com/travis-ci/travis-cookbooks/tree/master/co >> okbooks/travis_java/recipes >> >> < >> >> https://github.com/travis-ci/travis-cookbooks/tree/master/co >> okbooks/travis_java/recipes>. >> >> Which, as Amey noted earlier, jacoco seems to be utilizing >> >> https://github.com/jacoco/jacoco/blob/master/.travis.yml#L14-L23 < >> >> https://github.com/jacoco/jacoco/blob/master/.travis.yml#L14-L23>. >> >> >> >> I’m not particularly looking for any responses to this email. I more >> just >> >> wanted to document my current research efforts here. >> >> >> >> Cheers, >> >> -Rob >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> -- --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
