[
https://issues.apache.org/jira/browse/CASSANDRA-18285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17693646#comment-17693646
]
Michael Semb Wever commented on CASSANDRA-18285:
------------------------------------------------
If this is true, that in non-trunk branches there are forward upgrade paths and
a different jdk (i.e. 11) needs to be selected, then this applies to
cassandra-4.0 branch as well.
ci-cassandra.a.o (before 18133) does not do such jdk selection in-tree, so no
ticket is needed for that work.
> Add JDK 11 upgrade tests for 4.1+
> ---------------------------------
>
> Key: CASSANDRA-18285
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18285
> Project: Cassandra
> Issue Type: Task
> Components: CI
> Reporter: Ekaterina Dimitrova
> Priority: Normal
> Fix For: 4.1.x, 4.x
>
>
> Currently we test upgrades with Java 8, in preparation to drop it we need
> first to ensurer we test with 11. This has to be added not only in trunk,,
> but also 4.1
> I believe [~mck] has this ready to push in Jenkins at some point so this
> ticket should accommodate the addition of those upgrade tests in CircleCI for
> 4.1 and trunk.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
