[ 
https://issues.apache.org/jira/browse/CASSANDRA-18285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17728611#comment-17728611
 ] 

Michael Semb Wever commented on CASSANDRA-18285:
------------------------------------------------

We will need to filter out upgrade tests that are not valid with the current 
jdk.
If/Where forward-upgrade tests exist, they will only be run (not skipped) when 
the jdk is the common jdk for that version and the forward version. The 
consequence of this is that we would need to run upgrade tests twice, on each 
jdk, to ensure all upgrade tests are run. (They would not be duplicated, as 
upgrade tests would only run on the default/lowest common jdk that exists on 
the upgrade path.)

> Add JDK 11 upgrade tests for 4.0+ in CircleCI
> ---------------------------------------------
>
>                 Key: CASSANDRA-18285
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-18285
>             Project: Cassandra
>          Issue Type: Task
>          Components: CI
>            Reporter: Ekaterina Dimitrova
>            Assignee: Ekaterina Dimitrova
>            Priority: Normal
>             Fix For: 4.0.x, 4.1.x, 5.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

Reply via email to