[
https://issues.apache.org/jira/browse/CASSANDRA-17869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17645613#comment-17645613
]
Michael Semb Wever commented on CASSANDRA-17869:
------------------------------------------------
bq. It seems the argument so far is "so there are some differences in the build
process for both, and I agree that you should be explicit about building with a
jvm that is not the same one the release binaries will be built with"
The release scripts will ensure releases are only built with the default. CI
will check both for you.
We can add a warning if you are building with the non-default, I'm not sure of
the real value of doing more than that.
Thanks for taking it to the list, I'll raise it there.
bq. If we are going to anyway still have the logic in cassandra-builds for
fallback, I would suggest we focus here on doing that and have another ticket
for improvement for adding build scripts for trunk in .build. What do you think?
It adds complexity to the existing scripts that I am hoping to avoid.
> 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
>
> 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]
