Following this up, CASSANDRA-16989 allows to pass CircleCI env vars to the config generation script. For example, to set mid resources and the dtest branch and repo one can run:
.circleci/generate.sh -m \ -e DTEST_REPO=git://github.com/adelapena/cassandra-dtest.git \ -e DTEST_BRANCH=CASSANDRA-8272 As another example, to set the test multiplexer with highres: generate.sh -h \ -e REPEATED_UTEST_TARGET=testsome \ -e REPEATED_UTEST_CLASS=org.apache.cassandra.cql3.ViewTest \ -e REPEATED_UTEST_METHODS=testCompoundPartitionKey,testStaticTable \ -e REPEATED_UTEST_COUNT=100 This should allow to generate the config file without manually editing files in most cases. On Wed, 1 Sept 2021 at 19:46, Andrés de la Peña <adelap...@apache.org> wrote: > Hi all, > > Just to inform that now it's possible to generate CircleCI's config.yml > from the config-2_1.yml for a specific low/mid/high resource configuration > using the new -l/-m/-h flags. For example, ".circleci/generate.sh -h" will > generate a config.yml file for high resources. > > This might be useful when editing the CircleCI config env vars, for > example to set the dtest repo or to use the test multiplexer. This process > usually involves swapping the config.yml file to get the proper resources > and then to manually edit the multiple mentions > of DTEST_REPO, DTEST_BRANCH, etc. in the swapped file. With the new flags > one can instead just edit the single mention of the vars in the > config-2_1.yml file and then run the generation script to validate the > config and generate the modified config.yml with the desired resources > configuration. > > The new flags have been introduced by CASSANDRA-16871 and they are > mentioned in the readme for CircleCI: > https://github.com/apache/cassandra/blob/trunk/.circleci/readme.md > > >