[ https://issues.apache.org/jira/browse/CASSANDRA-19635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17846744#comment-17846744 ]
Bret McGuire commented on CASSANDRA-19635: ------------------------------------------ Of relevance here: there's an [ongoing conversation|https://lists.apache.org/thread/y3xfkypd7v2n3xmp9b75ob1c6xngo572] around bringing ccm in as a subproject of the Cassandra project. > Update target Cassandra versions for integration tests, support new 5.0.x > ------------------------------------------------------------------------- > > Key: CASSANDRA-19635 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19635 > Project: Cassandra > Issue Type: Task > Components: Client/java-driver > Reporter: Bret McGuire > Priority: Normal > > {color:#172b4d}[CASSANDRA-19292|https://issues.apache.org/jira/browse/CASSANDRA-19292] > added support for running integration tests against Cassandra 4.1.x but we > still need the ability to run against Cassandra 5.0.x. As of this writing we > need [riptano/ccm|https://github.com/riptano/ccm] to manage Cassandra 5.0.x > clusters. The DataStax CI infrastructure, however, uses a private fork of > ccm which adds the ability to manage DSE clusters (something riptano/ccm > can't do right now). So we presumably need to do one of the following: > {color} > * Port Cassandra 5.0.x support to the private fork > * Port DSE support to riptano/ccm > * Change the build process to install both riptano/ccm and the private fork > into distinct venvs and manage accordingly -- 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