[
https://issues.apache.org/jira/browse/CASSANDRA-18731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17789104#comment-17789104
]
Michael Semb Wever commented on CASSANDRA-18731:
------------------------------------------------
Today, our 5.0+ requirements to the CI pre-commit pipeline are
- artifacts, deb, redhat, checks (jdk11+17, amd+arm)
- stress, fqltool, burn, test, test-cdc, test-compression, test-oa, test-trie,
test-system-keyspace-directory, long-test, (jdk11+17)
- simulator-dtest (only jdk11)
- cqlsh (jdk11+17, multiple pythons, and cpython)
- jvm-dtest, jvm-dtest-novnode, dtest, dtest-large, dtest-novnode,
dtest-offheap, dtest-large-novnode (jdk11+17)
- jvm-dtest-upgrade, jvm-dtest-upgrade-novnode, dtest-upgrade,
dtest-upgrade-large, dtest-upgrade-novnode, dtest-upgrade-novnode-large (jdk11*)
- repeated runs
Notes:
- test-trie and dtest-offheap will be replaced with test-latest and
dtest-latest (see CASSANDRA-18753),
- long-test should also have the
cdc,compression,oa,latest,system-keyspace-directory variations,
- upgrade tests can use different jdks, only tests with an upgrade path that
have a common overlapping jdk are run, i.e only jdk17 can used for 5.0-5.1
updates and would have to be used for any forward upgrades to a 6.0 that didn't
support jdk11 – yes there are forward upgrades)
- circleci also does a build-jdk11-run-jdk17, which does not appear to be of
much additional value despite it being a more common use-case (see slack
discussion)
- simulator-dtest isn't running jdk17 because that's currently broken, ref
CASSANDRA-18616
- redhat has almalinux and centos7 variants
> Add declarative root CI structure
> ---------------------------------
>
> Key: CASSANDRA-18731
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18731
> Project: Cassandra
> Issue Type: Improvement
> Components: CI
> Reporter: Josh McKenzie
> Assignee: Josh McKenzie
> Priority: Normal
> Fix For: 5.x
>
>
> Currently we have a somewhat declarative structure in .circleci, however
> there's still quite a bit that's baked in (resource limitations, parallelism,
> which suites qualify for which pipelines (pre-commit vs. post-commit vs.
> ???), etc). Further, while CASSANDRA-18133 brings the build scripts in-tree,
> all these parameters (pipelines, env vars, job definitions, resource
> constraints) are all still scattered throughout the shell scripts and/or
> reliant on the {{JenkinsFile}} to determine what suites comprise what
> pipelines.
> This ticket aims to decouple the definition of pipelines and jobs for CI from
> the implementations themselves. The goal here is to define, establish, and
> test both the base config and some helper methods to provide _other_
> configurations (circle, ASF CI, etc) the tools they need to programmatically
> inherit base CI config from a purely declarative structure.
> Follow-up tickets will involve rewriting the in-tree build scripts and
> JenkinsFile generation to rely on this structure, as well as integrating the
> config parsing unit tests into our CI.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
