[
https://issues.apache.org/jira/browse/CASSANDRA-17939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17616606#comment-17616606
]
Josh McKenzie commented on CASSANDRA-17939:
-------------------------------------------
bq. That workflow tests building with j8 and running with both j8 and j11. The
j11 workflow is for both building and running with j11. We should be running
both workflows before committing.
Ah. I never realized that. To be fair I use David's script about 90% of the
time which has a different flow. Is that documented somewhere? Or is a user
just to infer "run all things w/pre-commit in the name"? Which is a reasonable
enough assertion to be fair.
Totally fine w/separate ticket(s) for follow-up stuff too. My instinct is to
play a little more fast and loose with the circleci generation stuff but that's
probably just bad behavior on my part. :)
> CircleCI: Automatically detect and repeat new or modified JUnit tests
> ---------------------------------------------------------------------
>
> Key: CASSANDRA-17939
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17939
> Project: Cassandra
> Issue Type: Task
> Components: CI
> Reporter: Andres de la Peña
> Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.x
>
>
> The purpose of this ticket is adding a new CircleCI job that automatically
> detects new or modified test classes and runs them repeatedly. That way we
> wouldn't need to manually specify those tests with {{.circleci/generate.sh}}.
--
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
