I'm assuming this is the script used for building the image ran by jenkins:
support/docker_build.sh If so, I can verify that this is what is causing the failure. Running manually on my local machine: CONFIGURATION="--verbose --enable-libevent --enable-ssl" COMPILER="gcc" OS="centos:7" support/docker_build.sh results in the same failure. And it stems from the following packages being installed: java-1.7.0-openjdk x86_64 1:1.7.0.91-2.6.2.3.el7 base 207 k java-1.7.0-openjdk-devel x86_64 1:1.7.0.91-2.6.2.3.el7 base 9.2 M java-1.7.0-openjdk-headless x86_64 1:1.7.0.91-2.6.2.3.el7 base 25 M java-1.8.0-openjdk x86_64 1:1.8.0.65-3.b17.el7 base 215 k java-1.8.0-openjdk-headless x86_64 1:1.8.0.65-3.b17.el7 base 31 M we either need to install java-1.8.0-openjdk-devel instead of java-1.7.0-openjdk-devel, or move things around such that maven is installed AFTER we install java-1.7.0-openjdk-devel so that its dependence on java doesn't automatically pull in java-1.8.0-openjdk. On Wed, Dec 16, 2015 at 1:11 PM, Kevin Klues <[email protected]> wrote: > Hey all, > > Jenkins builds are now consistently failing for centos 7, withe the failure: > > checking value of Java system property 'java.home'... > /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-3.b17.el7.x86_64/jre > configure: error: could not guess JAVA_HOME > > I ran into this problem a few days ago while building a vagrant box > for centos 7. The problem is summarized in this review request: > > https://reviews.apache.org/r/41371/ > > I'm not familiar with how the docker images for the build are > launched, but it seems they need to be updated in a manner similar to > what I propose in the updated getting started guide in the review. > > -- > ~Kevin -- ~Kevin
