natas_hw
/
cassandra
mirror of https://github.com/apache/cassandra
0
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
cassandra/.circleci
History
Stefan Podkowinski 7333c2b04d Refactor Circle CI configuration 
Enable high resource settings by copying .circleci/config.yml.HIGHRES
to .circleci/config.yml. For more details, see .circleci/readme.md

Patch by Stefan Podkowinski; reviewed by marcuse for CASSANDRA-14806
 		2019-03-15 09:47:27 +00:00
..
config-2_1.yml Refactor Circle CI configuration 2019-03-15 09:47:27 +00:00
config-2_1.yml.high_res.patch Refactor Circle CI configuration 2019-03-15 09:47:27 +00:00
config.yml Refactor Circle CI configuration 2019-03-15 09:47:27 +00:00
config.yml.HIGHRES Refactor Circle CI configuration 2019-03-15 09:47:27 +00:00
config.yml.LOWRES Refactor Circle CI configuration 2019-03-15 09:47:27 +00:00
generate.sh Refactor Circle CI configuration 2019-03-15 09:47:27 +00:00
readme.md Refactor Circle CI configuration 2019-03-15 09:47:27 +00: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;

  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 config-2_1.yml.HIGHRES