[
https://issues.apache.org/jira/browse/CASSANDRA-18011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Derek Chen-Becker reassigned CASSANDRA-18011:
---------------------------------------------
Assignee: Derek Chen-Becker
> Parameterize and generate .circleci/config-2_1.yml rather than manually
> maintain
> --------------------------------------------------------------------------------
>
> Key: CASSANDRA-18011
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18011
> Project: Cassandra
> Issue Type: Task
> Components: CI
> Reporter: Josh McKenzie
> Assignee: Derek Chen-Becker
> Priority: Normal
>
> Reference email thread [DISCUSS] Potential circleci config and workflow
> changes, specifically David's message
> [here|https://lists.apache.org/thread/059c4s6v8q9rl5lmhkj8xhfmwdj2fy2d]
> To quote him:
> bq. CI is a combinatorial problem, we need to run all jobs for all JDKs,
> vnode on/off, cdc on/off, compression on/of, etc…. But this is currently
> controlled and fleshed out by humans who want to add new jobs. We should move
> away from maintaining .circleci/config-2_1.yml and instead auto-generate it.
> Simple example of this problem is jdk11 support… we run a subset of tests on
> jdk11 and say its supported… will jdk17 have the same issue? Will it be even
> less tests? Why does the burden lie on everyone to “do the right thing” when
> all they want is a simple job?
> Derek Chen-Becker has also started a more granular email thread with a
> potential design alternative along these lines available
> [here|https://lists.apache.org/thread/mvql1p5y2j7so18427zcg4zxc9vzl7l3].
> Based on the output of those discussions, we should reflect the conclusion
> here and track that work.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
