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

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

bq. I am not sure what is the new part as I see one squashed commit and some 
time passed since I looked at this work. Can you advise, please?

Apologies (I can avoid further squashes on next update).

Not much changed …
– the `export CASSANDRA_USE_JDK17=true` lines were removed, 
– three jdks are in the matrix for trunk temporarily, see 
[here|https://github.com/apache/cassandra-builds/compare/trunk...thelastpickle:cassandra-builds:mck/17869#diff-1f760d89dfb81ea05a11d862007a4e4e586b38aac7ae87f62c5b2e86571809c0R112]
– how jdk17 support is detected was updated 
[here|https://github.com/apache/cassandra-builds/compare/trunk...thelastpickle:cassandra-builds:mck/17869#diff-f458d745bb6227c4f9161c75ffed2a98d0ee3cd7da734afe7e759670c5969b3cR45-R50]

> 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: 4.x
>
>          Time Spent: 2.5h
>  Remaining Estimate: 0h
>
> Add JDK17 option to cassandra-builds build-scripts, they only currently 
> support options {{8}} and {{1}}.
> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to