Incorrect PATH in nightly builds

[ashu-mehra]

In nightly docker images of openjdk8-openj9, jdk is present at /opt/java/openjdk/jdk8u172-b11, but the PATH is set to /opt/java/openjdk/jdk8u162-b12/bin.

$ docker run --rm -v $PWD:/tmp adoptopenjdk/openjdk8-openj9:nightly java -version
docker: Error response from daemon: oci runtime error: container_linux.go:247: starting container process caused "exec: \"java\": executable file not found in $PATH".
ERRO[0000] error getting events from daemon: context canceled

$ docker run --rm -it -v $PWD:/tmp adoptopenjdk/openjdk8-openj9:nightly
root@cff5d039aaf4:/# echo $PATH
/opt/java/openjdk/jdk8u162-b12/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

Similarly, for openjdk9-openj9, jdk is present at /opt/java/openjdk/jdk-9.0.4+12 but PATH is set to /opt/java/openjdk/jdk-9+181/bin.

[chandrams]

@gdams - We had a discussion regarding the incorrect release name on slack, you mentioned this is being fixed as part of re-factoring the build scripts. Any update on this?

[dinogun]

This is resolved as the build paths are fixed in the openjdk-build repo