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

Brandon Williams commented on CASSANDRA-18106:
----------------------------------------------

If we 
[disable|https://github.com/driftx/cassandra-dtest/commit/e0c1a9ed329a3a15120c409f4317be1351488600]
 that code and just run with JAVA_HOME, the upgrade test [will 
pass|https://app.circleci.com/pipelines/github/driftx/cassandra/880/workflows/775218f7-8bdc-49ee-90e1-a00637c53502/jobs/12686].
  This is only because it's java8, however, since the upgrade_through_versions 
test starts at 2.2 and upgrades through majors up to trunk.  At some point, the 
jdk will need to actually switch in that lineage while the test is executing, 
which will probably require more information than a single JAVA_HOME provides.

> Update CCM for JDK17 and revise current JDK detection strategy
> --------------------------------------------------------------
>
>                 Key: CASSANDRA-18106
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-18106
>             Project: Cassandra
>          Issue Type: Task
>          Components: CI
>            Reporter: Ekaterina Dimitrova
>            Assignee: Brandon Williams
>            Priority: Normal
>             Fix For: 4.x
>
>
> 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. 



--
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