[CASSANDRA-18106] Update CCM for JDK17 and revise current JDK detection strategy

• Type: Task
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 5.0-alpha1, 5.0
• Component/s: CI
• Epic Link: Support Java 17
• Change Category: Quality Assurance
• Complexity: Normal
• Platform: All

Source Control Link

https://github.com/apache/cassandra/commit/5c51f05dab0562c3b95b60224e4698e2a30d2ce7 https://github.com/riptano/ccm/commit/f511ace22ce1ec3c0220f7b9e988d67d8d2d3197

Test and Documentation Plan

run CI

• Assignee: Brandon Williams
• Reporter: Ekaterina Dimitrova

Authors

Brandon Williams

Reviewers

Ekaterina Dimitrova, Michael Semb Wever

• Created: 09/Dec/22 16:42
• Updated: 16/May/24 14:00
• Resolved: 14/Mar/23 14:59

Description

As part of CASSANDRA-16895 initial POC an initial version of CCM patch was created. This needs to be revisited and reviewed

Recently we closed CASSANDRA-18039 which brought questions, probably we need to revise how we detect JDK versions in CCM and whether it is correct. To the best of my knowledge there are certain tests in the repo around that and they pass so my guess is we need to revise just the strategy and maybe document it explicitly or consider if we want any changes to be applied. Also, we need to be careful with breaking changes. 

Issue Links

• blocks: CASSANDRA-18247 Add CircleCI config files for J11+J17
• fixes: CASSANDRA-18293 Remove JAVA8_HOME and JAVA11_HOME from circle configs
• is related to: CASSANDRA-19636 Fix CCM for Cassandra 5.0 and add arg to the command line which let the user explicitly select JVM
• is related to: CASSANDRA-17869 Add JDK17 option to cassandra-builds (build-scripts and jenkins dsl) and on jenkins agents
• relates to: CASSANDRA-18285 [CircleCI] Add JDK 11 Java and Python upgrade tests in trunk
• relates to: CASSANDRA-18293 Remove JAVA8_HOME and JAVA11_HOME from circle configs