Hi Lars, though not directly relate to this topic, we'd like to set-up testing like the community Jenkins.
Are the jenkins scripts open-source? Could you share the configures of the Jenkins jobs? Looks like they're not in the Impala repo. I'm unable to browse the configures of jobs in jenkins.impala.io since I can't login. At 2018-07-10 02:34:44, "Lars Volker" <[email protected]> wrote: >Several developers seem to use Ubuntu for their development which makes me >think that Impala would work on Debian, too. However, I think we should not >claim proper support for Debian since to my knowledge there are no >automated Jenkins jobs verifying this. I am also not aware of anyone >developing or using Impala on Debian. > >Of course anyone in the community is free to set-up automated testing for >Debian, either on our project Jenkins or on their own infrastructure. > > > >On Fri, Jul 6, 2018 at 12:04 PM Jim Apple <[email protected]> >wrote: > >> Should we throw a Debian version in for good measure? >> >> https://github.com/apache/impala/search?q=debian >> >> On Fri, Jul 6, 2018 at 9:19 AM, Lars Volker <[email protected]> >> wrote: >> >> > Hi All, >> > >> > With the automatic commit flow to the 2.x branch being disabled, I'd like >> > to suggest that we deprecate support for some older operating systems on >> > the 3.x branch. This would allow us to get rid of almost all the checks >> in >> > common/config.h.in as well as some workarounds in the code. It would >> also >> > simplify the upcoming rebase of the KRPC code (IMPALA-7006). >> > >> > I'd like to propose that we pick Ubuntu 14.04, CentOS 6.8, and SLES 12 as >> > the minimum operating system versions on which Impala has to compile and >> > pass all tests. I'd also like to deprecate support for Java 7 and require >> > Java 8 for all changes going forward. To my knowledge these are the >> minimum >> > versions that people use for development and deployment of the 3.x >> branch. >> > >> > I'm curious what others think. >> > >> > Cheers, Lars >> > >>
