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

[FLINK-12516][travis] use Ubuntu 16.04 LTS (Xenial) and change to openJDK8 #8448

Merged
merged 1 commit into from
May 16, 2019

Conversation

NicoK
Copy link
Contributor

@NicoK NicoK commented May 15, 2019

What is the purpose of the change

This changes the test environment from trusty to xenial which is still
supported until 2021-04 and provides more up-to-date system libraries.

Since oraclejdk8 is not available in Travis' xenial image and we can't switch
to oraclejdk9 yet, this also changes the JDK to openJDK8.

Brief change log

  • change Travis' distribution to xenial
  • change Travis' JDK to openjdk8

Verifying this change

Run Travis tests.

Does this pull request potentially affect one of the following parts:

  • Dependencies (does it add or upgrade a dependency): no
  • The public API, i.e., is any changed class annotated with @Public(Evolving): no
  • The serializers: no
  • The runtime per-record code paths (performance sensitive): no
  • Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: no
  • The S3 file system connector: no

Documentation

  • Does this pull request introduce a new feature? no
  • If yes, how is the feature documented? not applicable

…nJDK8

This changes the test environment from trusty to xenial which is still
supported until 2021-04 and provides more up-to-date system libraries.

Since oraclejdk8 is not available in Travis' xenial image and we can't switch
to oraclejdk9 yet, this also changes the JDK to openJDK8.
@NicoK NicoK requested a review from zentol May 15, 2019 11:31
@flinkbot
Copy link
Collaborator

Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community
to review your pull request. We will use this comment to track the progress of the review.

Review Progress

  • ❓ 1. The [description] looks good.
  • ❓ 2. There is [consensus] that the contribution should go into to Flink.
  • ❓ 3. Needs [attention] from.
  • ❓ 4. The change fits into the overall [architecture].
  • ❓ 5. Overall code [quality] is good.

Please see the Pull Request Review Guide for a full explanation of the review process.


The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commands
The @flinkbot bot supports the following commands:

  • @flinkbot approve description to approve one or more aspects (aspects: description, consensus, architecture and quality)
  • @flinkbot approve all to approve all aspects
  • @flinkbot approve-until architecture to approve everything until architecture
  • @flinkbot attention @username1 [@username2 ..] to require somebody's attention
  • @flinkbot disapprove architecture to remove an approval you gave earlier

@zentol zentol self-assigned this May 16, 2019
@zentol zentol merged commit 54c1af1 into apache:master May 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants