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
