1) would be nice to have. The first thing I do is that I change the parallelism to 20. None of committed config.yaml's are appropriate for our company CircleCI so I have to tweak this manually. I think we can not run more that 25/30 containers in parallel, something like that. HIGHRES has 100 and MIDRES has some jobs having parallelism equal to 50 or so so that is not good either. I would be happy with simple way to modify default config.yaml on parallelism. I use "sed" to change parallelism: 4 to parallelism: 20 and leave parallelism: 1 where it does not make sense to increase it. However I noticed that there is not "4" set everywhere, some jobs have it set to "1" so I have to take extra care of these cases (I consider that to be a bug, I think there are two or three, I do not remember). Once set, I have that config in "git stash" so I just apply it every time I need it.
5) would be nice too. 7) is nice but not crucial, it takes no time to commit that. ________________________________________ From: Josh McKenzie <jmcken...@apache.org> Sent: Wednesday, October 19, 2022 21:50 To: dev Subject: [DISCUSS] Potential circleci config and workflow changes NetApp Security WARNING: This is an external email. Do not click links or open attachments unless you recognize the sender and know the content is safe. While working w/Andres on CASSANDRA-17939 a variety of things came up regarding our circleci config and opportunities to improve it. Figured I'd hit the list up here to see what people's thoughts are since many of us intersect with these systems daily and having your workflow disrupted without having a chance to provide input is bad. The ideas: 1. Tune parallelism levels per job (David and Ekaterina have insight on this) 2. Rename jobs on circle to be more indicative of their function 3. Unify j8 and j11 workflow pairs into single (for 2 and 3 see: https://issues.apache.org/jira/browse/CASSANDRA-17939?focusedCommentId=17616595&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17616595) 4. Update documentation w/guidance on using circle, .circleci/generate.sh examples, etc 4a. How to commit: https://cassandra.apache.org/_/development/how_to_commit.html 4b. Testing: https://cassandra.apache.org/_/development/testing.html 5. Flag on generate.sh to allow auto-run on push 6. Clean up the -l, -m, -h flags (test and indicate -l feasibility for all suites, default to -m, deprecate -h?) <- may not be a code-change issue and instead be a documentation issue 7. Consider flag on generate.sh to run and commit with "[DO NOT MERGE] temporary circleci config" as the commit message Curious to see what folks think. ~Josh
