Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Travis CI to use Ubuntu Bionic (18.04) #413

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

mbrukman
Copy link

@mbrukman mbrukman commented Jul 16, 2020

The default is Ubuntu Xenial (16.04) as per:
https://docs.travis-ci.com/user/reference/overview/#linux

Also switch from Oracle JDK 8 to OpenJDK 8, since Oracle JDK 8 is no longer
available, as per https://travis-ci.org/github/metal/metal.js/builds/708924115

$ ~/bin/install-jdk.sh --target "/home/travis/oraclejdk8" --workspace "/home/travis/.cache/install-jdk" --feature "8" --license "BCL"
Ignoring license option: BCL -- using GPLv2+CE by default
install-jdk.sh 2020-06-02
Expected feature release number in range of 9 to 16, but got: 8
The command "~/bin/install-jdk.sh --target "/home/travis/oraclejdk8" --workspace "/home/travis/.cache/install-jdk" --feature "8" --license "BCL"" failed and exited with 3 during .

The default is Ubuntu Xenial (16.04) as per:
https://docs.travis-ci.com/user/reference/overview/#linux

Also switch from Oracle JDK 8 to OpenJDK 8, since Oracle JDK 8 is no longer
available, as per https://travis-ci.org/github/metal/metal.js/builds/708924115

> $ ~/bin/install-jdk.sh --target "/home/travis/oraclejdk8" --workspace "/home/travis/.cache/install-jdk" --feature "8" --license "BCL"
> Ignoring license option: BCL -- using GPLv2+CE by default
> install-jdk.sh 2020-06-02
> Expected feature release number in range of 9 to 16, but got: 8
> The command "~/bin/install-jdk.sh --target "/home/travis/oraclejdk8" --workspace "/home/travis/.cache/install-jdk" --feature "8" --license "BCL"" failed and exited with 3 during .
@mbrukman
Copy link
Author

The build is currently failing (with no changes in this PR), see issue #415 for details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant