[
https://issues.apache.org/jira/browse/CASSANDRA-17869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17643513#comment-17643513
]
Josh McKenzie commented on CASSANDRA-17869:
-------------------------------------------
bq. i'm wondering if all this would be simpler if we brought these* scripts
in-tree
I've been asking myself this same question. Having them separate has some real
costs in terms of visibility and folks on the project being familiar with it,
but versioning the build scripts separately and having a single repo that has
multi-version support makes some logical sense that we'd lose if we put it
in-tree.
Would the idea be to have build scripts that are targeted per-branch rather
than all the scripts on trunk supporting all previous supported branches? Or
the latter?
> 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
> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
