[
https://issues.apache.org/jira/browse/CASSANDRA-16625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17339029#comment-17339029
]
Andres de la Peña commented on CASSANDRA-16625:
-----------------------------------------------
The patches in the current generation script are for the {{config-2_1.yml}}
file, so first we patch and then we generate the final
{{config.yml[.LOWRES|.MIDRES|.HIGHRES]}} file with the CircleCI CLI, using the
command {{circleci config process}}. That's in line with the idea of never
editing the {{config.yml}} manually.
However {{circleci config process}} gets rid of the pipeline parameters, so we
would need to add another set of patches for the final
{{config.yml[.LOWRES|.MIDRES|.HIGHRES]}} files. Since these files are generated
automatically, I'm afraid that different versions of the CircleCI tool could
produce different final resource files. That could make patching those files a
more manual process, with an increased risk of wrongly applying the parameters
changes to them. It's not that we can't do it, but just that we would make the
process of editing the CircleCI config more difficult.
By the way, I have also observed that the CircleCI CLI tool also removes the
license header when generating the config, so the current
{{.circleci/generate.sh}} also requires some minor manual intervention to add
the missed licenses. I have included a fix for this in the patch.
> Add a CircleCI job to run some tests repeatedly
> -----------------------------------------------
>
> Key: CASSANDRA-16625
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16625
> Project: Cassandra
> Issue Type: Task
> Components: CI
> Reporter: Andres de la Peña
> Assignee: Andres de la Peña
> Priority: Normal
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I think it could be useful to have an optional CircleCI job to run some
> specific tests n times. That way, tickets could attach CircleCI runs showing
> that the changes don't make a certain ticket flaky or, conversely, that they
> fix a flaky test. Doing this systematically should mitigate the risk of
> introducing new flaky tests, and I guess it would be more convenient and easy
> to share than running the tests locally or on a private CI system.
> It would also be nice to have something similar in Jenkins, but I'm focusing
> this ticket on CircleCI because it's available also for non-committers, so
> assignees can run their tests before setting the tickets as ready for review.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
