cassandra/.circleci
Mick Semb Wever 7337fc0ab4
Merge branch 'cassandra-3.11' into trunk
2021-04-19 17:39:10 +02:00
..
config-2_1.yml Merge branch 'cassandra-3.11' into trunk 2021-04-19 17:39:10 +02:00
config-2_1.yml.high_res.patch Circleci should run cqlshlib tests as well 2020-11-05 15:43:17 -08:00
config-2_1.yml.mid_res.patch Updated default num_tokens from 256 to 16 with associated allocate_tokens_for_local_replication_factor set to 3 2020-12-17 22:18:17 +01:00
config.yml Merge branch 'cassandra-3.11' into trunk 2021-04-19 17:39:10 +02:00
config.yml.HIGHRES Merge branch 'cassandra-3.11' into trunk 2021-04-15 13:13:09 +02:00
config.yml.LOWRES Merge branch 'cassandra-3.11' into trunk 2021-04-15 13:13:09 +02:00
config.yml.MIDRES Merge branch 'cassandra-3.11' into trunk 2021-04-15 13:13:09 +02:00
generate.sh Merge branch 'cassandra-3.11' into trunk 2021-04-19 17:39:10 +02:00
readme.md Merge branch 'cassandra-3.11' into trunk 2021-04-19 17:39:10 +02:00

readme.md

CircleCI config files

Switching to high resource settings

This directory contains generated files for high and low resource settings. Switch between them by copying the correct file to config.yml and committing the result;

cp .circleci/config.yml.HIGHRES .circleci/config.yml

config.yml.LOWRES is the default config. MIDRES and HIGHRES are custom configs for those who have access to premium CircleCI resources.

Make sure you never edit the config.yml manually.

Updating the config master

To update the config (other than just swapping high/low resources) you need to install the CircleCI CLI.

The directory contains config-2_1.yml which is then converted to the actual HIGH/MID/LOW resource files. There is a script called generate.sh which creates the LOWRES, MIDRES, and HIGHRES files, read below for details how to do it manually;

  1. make your edits to config-2_1.yml - let it stay at lowres settings
  2. generate a valid LOWRES file: circleci config process config-2_1.yml > config.yml.LOWRES
  3. then apply the highres patch to config-2_1.yml; patch -o config-2_1.yml.HIGHRES config-2_1.yml config-2_1.yml.high_res.patch (this creates a new file config-2_1.yml.HIGHRES instead of in-place patching config-2_1.yml) Note that if the patch no longer applies to config-2_1.yml a new patch file is needed, do this by manually making config-2_1.yml high resource and create the patch file based on the diff (don't commit it though).
  4. generate the HIGHRES file: circleci config process config-2_1.yml.HIGHRES > config.yml.HIGHRES
  5. and remove the temporary patched HIGHRES file: rm config-2_1.yml.HIGHRES