Skip to content

ci: test JDK 27 instead of 21 in nightly builds - #3797

Closed
pjfanning wants to merge 1 commit into
apache:mainfrom
pjfanning:nightly-jdk27
Closed

pjfanning wants to merge 1 commit into
apache:mainfrom
pjfanning:nightly-jdk27

Conversation

@pjfanning

Copy link
Copy Markdown
Member

Motivation

JDK 17 is the minimum and JDK 25 the latest LTS, so those bound the supported range. It is more useful to see how Pekko behaves on the latest non-LTS release than to keep testing JDK 21.

Modification

Change the jdk-nightly-build matrix in nightly-builds.yml from [17, 21, 25] to [17, 25, 27]. JDK 27 picks up the existing -ge 25 / -ge 21 settings (timefactor 4, minimum-runnable 8, virtualized dispatchers).

Result

Nightly builds cover JDK 17, 25 and 27.

Tests

  • Not run - CI workflow change only; nightly CI will exercise it

References

None - CI matrix update

Motivation:
JDK 17 is the minimum and JDK 25 the latest LTS, so those bound the
supported range. It is more useful to see how Pekko behaves on the
latest non-LTS release than to keep testing JDK 21.

Modification:
Change the jdk-nightly-build matrix from [17, 21, 25] to [17, 25, 27].

Result:
Nightly builds cover JDK 17, 25 and 27.

Tests:
- Not run - CI workflow change only; nightly CI will exercise it

References:
None - CI matrix update
pjfanning added a commit to apache/pekko-http that referenced this pull request Nov 17, 2026
Motivation:
JDK 17 is the minimum and JDK 25 the latest LTS, so those bound the
supported range. It is more useful to see how Pekko HTTP behaves on the
latest non-LTS release than to keep testing JDK 21.

Modification:
Change the nightly compile-and-test JDK matrix from [17, 21, 25] to
[17, 25, 27].

Result:
Nightly builds cover JDK 17, 25 and 27.

Tests:
- Not run - CI workflow change only; nightly CI will exercise it

References:
None - CI matrix update; matches apache/pekko#3797
@pjfanning

Copy link
Copy Markdown
Member Author

Closing: the same change in pekko-http broke its nightly build. JDK 27 compilation fails with Unsupported class file major version 71 because Scala 2.13.18 and 3.3.9 bundle ASM versions that cannot read JDK 27 class files (failed job). pekko-http is dropping JDK 27 in apache/pekko-http#1498. This can be revisited once Scala 2.13.19 and 3.3.10 ship with JDK 27 support.

@pjfanning pjfanning closed this Nov 18, 2026
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.

1 participant