[MESOS-4184] Jenkins builds for Centos fail with missing 'which' utility and incorrect 'java.home'

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.27.0
• Labels: mesosphere

Environment

centos 7

• Target Version/s: 0.27.0
• Sprint: Mesosphere Sprint 24
• Story Points: 3
• Assignee: Kevin Klues
• Reporter: Kevin Klues
• Shepherd: Joris Van Remoortere
• Created: 16/Dec/15 21:58
• Updated: 26/Nov/18 12:22
• Resolved: 26/Nov/18 12:22

Description

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

They also fail early on during 'bootstrap' with a missing 'which' command.

The solution is to update support/docker_build.sh to install 'which' as well as make sure the proper versions of java are installed during the installation process.

The problem here is that we install maven BEFORE installing java-1.7.0-openjdk-devel, causing maven to pull in a dependency on java-1.8.0-openjdk. This causes problems with finding the proper java.home in our mesos/configure script because of the mismatch between the most up to date jre (1.8.0) and the most up to date development tools (1.7.0). We can either update the script to pull in the 1.8 devel tools or move our dependence on maven until AFTER our installation of java-1.7.0-openjdk-devel. Unclear what the best solution is.