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

[build] Build with Microsoft OpenJDK 21.0.5 #9683

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

pjcollins
Copy link
Member

@pjcollins pjcollins commented Jan 14, 2025

Context: #9651
Context: 14a6bfb

Updates the macOS, Windows, and Linux build stages to install and build with Microsoft OpenJDK 21.0.5.

The nightly test jobs have also been updated to use JDK 21, while all other test jobs should continue to use JDK 17.

As of 14a6bfb, main/.NET 10 supports both JDK 17 and 21.

The default version that VS and the InstallAndroidDependencies target will install is JDK 17, though we may want to upgrade this to 21 as we move further into the .NET 10 cycle.

As of this PR, all explicit test stages that run against regular PR/CI will continue to use JDK 17. The build jobs, Windows smoke tests, and nightly test jobs will build and test against JDK 21. JDK 11 support was technically removed in df68c20, though I believe customers can add <MinimumSupportedJavaVersion>11.0</MinimumSupportedJavaVersion> to their project files to use it. Some test coverage for this exists in ValidateJavaVersionTests, but this scenario is not tested end to end.

Context: #9651
Context: 14a6bfb

Updates the macOS, Windows, and Linux build stages to install and build
with Microsoft OpenJDK 21.0.5.

The macOS MSBuild tests and nightly APK tests have also been updated to
use JDK 21, while all other test jobs should continue to use JDK 17.
@pjcollins
Copy link
Member Author

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@pjcollins pjcollins marked this pull request as ready for review January 15, 2025 16:40

Choose a reason for hiding this comment

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

Copilot reviewed 5 out of 8 changed files in this pull request and generated no comments.

Files not reviewed (3)
  • build-tools/xaprepare/xaprepare/Steps/Step_InstallAdoptOpenJDK.cs: Evaluated as low risk
  • build-tools/automation/yaml-templates/variables.yaml: Evaluated as low risk
  • build-tools/xaprepare/xaprepare/Steps/Step_GenerateFiles.cs: Evaluated as low risk
@jpobst
Copy link
Contributor

jpobst commented Jan 15, 2025

For those of us out of the loop, can you elaborate on what this means for our customers and our CI?

  • What version(s) of JDK will we support in .NET 10?
  • If multiple, what version will be the default in .NET 10?
  • If multiple, are we running tests on those versions? (This PR seems to remove our JDK-11 nightly tests.)

Once committed, anything that is new for .NET 10 should be documented here: #9571.

@pjcollins
Copy link
Member Author

For those of us out of the loop, can you elaborate on what this means for our customers and our CI?

  • What version(s) of JDK will we support in .NET 10?
  • If multiple, what version will be the default in .NET 10?
  • If multiple, are we running tests on those versions? (This PR seems to remove our JDK-11 nightly tests.)

Once committed, anything that is new for .NET 10 should be documented here: #9571.

  • As of 14a6bfb, main/.NET 10 supports both JDK 17 and 21.
  • The default version that VS and the InstallAndroidDependencies target will install is JDK 17, though we may want to upgrade this to 21 as we move further into the .NET 10 cycle?
  • As of this PR, all explicit test stages that run against regular PR/CI will continue to use JDK 17. The build jobs, Windows smoke tests, and nightly test jobs will build and test against JDK 21. JDK 11 support was technically removed in df68c20, though I believe customers can add <MinimumSupportedJavaVersion>11.0</MinimumSupportedJavaVersion> to their project files to use it. This is not a tested scenario.

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.

4 participants