History

Bereng 9c0f8902e8 Replace git:// with https:// in Circle CI config file patch by Berenguer Blasi; reviewed by Brandon Williams, Ekaterina Dimitrova and David Capwell for CASSANDRA-17255		2022-01-11 20:42:19 -05:00
..
config-2_1.yml	Replace git:// with https:// in Circle CI config file	2022-01-11 20:42:19 -05:00
config-2_1.yml.high_res.patch	Use testclasslist for jvm dtests in circleci	2020-01-29 09:31:47 +01:00
config.yml	Replace git:// with https:// in Circle CI config file	2022-01-11 20:42:19 -05:00
config.yml.HIGHRES	Replace git:// with https:// in Circle CI config file	2022-01-11 20:42:19 -05:00
config.yml.LOWRES	Replace git:// with https:// in Circle CI config file	2022-01-11 20:42:19 -05:00
generate.sh	Update Docker image for testing in CircleCI config	2021-11-11 20:29:09 -05:00
license.yml	Update Docker image for testing in CircleCI config	2021-11-11 20:29:09 -05:00
readme.md	Fix rat checking for files with missing license headers	2021-04-19 17:18:26 +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

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/LOW resource files. There is a script called generate.sh which creates the LOWRES and HIGHRES files, read below for details how to do it manually;

make your edits to config-2_1.yml - let it stay at lowres settings
generate a valid LOWRES file: circleci config process config-2_1.yml > config.yml.LOWRES
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).
generate the HIGHRES file: circleci config process config-2_1.yml.HIGHRES > config.yml.HIGHRES
and remove the temporary patched highres config-2_1.yml.HIGHRES