[
https://issues.apache.org/jira/browse/CASSANDRA-17869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17713100#comment-17713100
]
Ekaterina Dimitrova commented on CASSANDRA-17869:
-------------------------------------------------
{quote}Strictly speaking I think this is out-of-scope
{quote}
I am confused. When I asked for a separate ticket for upgrade tests you said
you will handle them here and you also initiated updating the upgrade paths.
With that said, I don't mind if you pull in a follow up ticket all upgrade
paths changes and we focus on bringing upgrade tests J11 to what we see
currently with J8. Please let me know.
{quote}This is not a problem, the grep against java.version.11 works on past
code too.
{quote}
(y)
{quote}No. Upgrade tests will use the lowest (default) JDK that is in common.
4.0 and 4.1 share JDK8 so that will be used for that path. I don't see the ROI
in testing additional JDKs here.
{quote}
(y)
> Add JDK17 option to cassandra-builds (build-scripts and jenkins dsl) and on
> jenkins agents
> ------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-17869
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17869
> Project: Cassandra
> Issue Type: Task
> Components: Build
> Reporter: Michael Semb Wever
> Assignee: Michael Semb Wever
> Priority: Normal
> Fix For: 5.x
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> Add JDK17 option to cassandra-builds build-scripts, they only currently
> support options {{8}} and {{11}}.
> Add JDK17 to the matrix axes in the jenkins dsl.
> Ensure JDK17 is installed on all the jenkins agents.
--
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
