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

Add JDK 11 to CI test matrix #395

Merged
merged 4 commits into from
Mar 2, 2022
Merged

Conversation

ohltyler
Copy link
Member

@ohltyler ohltyler commented Mar 2, 2022

Signed-off-by: Tyler Ohlsen [email protected]

Description

One of the campaigns for upcoming 1.3 release is testing on JDK 11, with optional versions of 8, 14, 17. This updates the workflow to add JDK 11. There are other problems with 8/17 so ignoring those for now.

Also removes CD workflow since that hasn't been used since pre-OpenSearch days.

Issues Resolved

Resolves #320

Check List

  • Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@ohltyler ohltyler requested a review from a team March 2, 2022 19:03
ohltyler added 2 commits March 2, 2022 11:03
Signed-off-by: Tyler Ohlsen <[email protected]>
Signed-off-by: Tyler Ohlsen <[email protected]>
@ohltyler ohltyler changed the title Add JDK 8, 11, 17 to CI test matrix Add JDK 8, 11 to CI test matrix Mar 2, 2022
Signed-off-by: Tyler Ohlsen <[email protected]>
@ohltyler ohltyler changed the title Add JDK 8, 11 to CI test matrix Add JDK 11 to CI test matrix Mar 2, 2022
@ohltyler ohltyler mentioned this pull request Mar 2, 2022
16 tasks
Copy link
Member

@amitgalitz amitgalitz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, just make sure to wait until CI passes especially as this involves CI workflow changes. Also JDK8 might not be working because of protostuff dependency compiled with java 11, before that change was pushed it in, it was okay to use runtime jdk8. However the exception itself mentions something was compiled with java version 54 which is equivalent to java 10 so not 100% sure. Can be addressed in future PRs

Build-ad:
strategy:
matrix:
java: [14]
java: [11, 14]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All plugins and OpenSearch core should make sure Java 11 works for 1.3 release?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

11 is the default used by bundle build / integ tests

@ohltyler ohltyler merged commit 2bf3b0d into opensearch-project:main Mar 2, 2022
@ohltyler ohltyler deleted the update-ci branch March 2, 2022 19:53
opensearch-trigger-bot bot pushed a commit that referenced this pull request Mar 2, 2022
Signed-off-by: Tyler Ohlsen <[email protected]>
(cherry picked from commit 2bf3b0d)
ohltyler added a commit that referenced this pull request Mar 2, 2022
Signed-off-by: Tyler Ohlsen <[email protected]>
(cherry picked from commit 2bf3b0d)
@ohltyler ohltyler added the infra Changes to infrastructure, testing, CI/CD, pipelines, etc. label Mar 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport 1.x infra Changes to infrastructure, testing, CI/CD, pipelines, etc.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Default CI Java Version to Java 11, run tests on 8, 14 and 17
3 participants