[
https://issues.apache.org/jira/browse/CASSANDRA-19414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17820729#comment-17820729
]
Stefan Miklosovic commented on CASSANDRA-19414:
-----------------------------------------------
I have never done that and I think it is a bad practice in general. In a lot of
cases one config is not even applicable to the other because of the differences
in CircleCI plan, parallelism, resource classes etc ... that commit has even
such commit message "DO NOT COMMIT".
> Skinny dev circle workflow
> --------------------------
>
> Key: CASSANDRA-19414
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19414
> Project: Cassandra
> Issue Type: Improvement
> Components: CI
> Reporter: Berenguer Blasi
> Assignee: Berenguer Blasi
> Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> CircleCi CI runs are getting pretty heavy. During dev iterations we trigger
> many CI pre-commit jobs which are just an overkill.
> This ticket has the purpose to purge from the pre-commit workflow all
> variations of the test matrix but the vanilla one. That should enable us for
> a quick and cheap to iterate *during dev*, this is not a substitute for
> pre-commit . This ticket's work will serve as the basis for the upcoming
> changes being discussed
> [atm|https://lists.apache.org/thread/qf5c3hhz6qkpyqvbd3sppzlmftlc0bw0]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
