Install of oraclejdk11 has been failing all day with:
Downloading JDK from http://download.oracle.com/otn-pub/java/jdk/11.0.1+13/90cf5d8f270a4347a95050320eef3fb7/jdk-11.0.1_linux-x64_bin.tar.gz...
The command "~/bin/install-jdk.sh --target "/home/travis/oraclejdk11" --workspace "/home/travis/.cache/install-jdk" --feature "11" --license "BCL"" failed and exited with 8 during .
These sorts of transient failures happen a lot . What causes them?
I have tried to mitigate transient failures by enabling .m2 caching, but that does not solve the problem with JDK install failures. What is the right workaround for this?
Ah! So this would explain why this happens so often. Every time a new Java version is released, somebody has to update the download links in Travis, because Oracle quickly pulls the old download link.
Surely a script could be written to automatically find the highest available version number before the download attempt is started, rather than relying on hardcoded links?
The install-jdk.sh script does exactly this for -ea versions of OpenJDK.
JDK versions that are released to GA shouldn’t need install-jdk.sh at all. They could be pre-installed and updated via another mechanism. E.g. jdk: openjdk-11 always points to a valid OpenJDK 11 installation. Be it 11.0.1 or 11.0.2 some days later is up to Travis’ to provide.
Looks like Oracle JDK 11.0.2 is now obsolete too and the download link has been removed…
Downloading JDK from https://download.java.net/java/GA/jdk11/7/GPL/openjdk-11.0.2_linux-x64_bin.tar.gz...
The command "~/bin/install-jdk.sh --target "/home/travis/openjdk11" --workspace "/home/travis/.cache/install-jdk" --feature "11" --license "GPL" --cacerts" failed and exited with 8 during .
I just ran into this too – so openjdk is not immune to these release version bumps. Since the -ea script looks for and then downloads the latest version, couldn’t the non-ea scripts do the same thing for point releases?
It could – but Oracle changes the pattern now and then, so I replaced the “smart” lookup code by pointing to static URLs. Normally, that works well. Unless a change happens GA…