mirror of https://github.com/apache/cassandra
- This removes lib/ from version control. - The generated pom files are now the source of truth to the project's depdendencies, and the lib/ folder re-created during the build from compile scope dependencies excluding provided and system scopes. Project dependencies are first downloaded to the maven local repository at `~/.m2/repository`. - Maven is now required to be installed to build, that is the `mvn` command needs to be found in the path. - The new resolver-ant-tasks targets have been encapsulated into the `build/build-resolver.xml` ant file. - Most classpaths in build.xml are replaced with resolver:resolve definitions. - The build-deps-pom generated pom file is now only used for declaring test dependencies. patch by Mick Semb Wever; reviewed by Brandon Williams for CASSANDRA-16557 |
||
|---|---|---|
| .. | ||
| config-2_1.yml | ||
| config-2_1.yml.high_res.patch | ||
| config-2_1.yml.mid_res.patch | ||
| config.yml | ||
| config.yml.HIGHRES | ||
| config.yml.LOWRES | ||
| config.yml.MIDRES | ||
| generate.sh | ||
| license.yml | ||
| readme.md | ||
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/mid/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;
- 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 - add the Apache license header to the newly created LOWRES file:
cat license.yml config.yml.LOWRES > config.yml.LOWRES.new && mv config.yml.LOWRES.new 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 fileconfig-2_1.yml.HIGHRESinstead of in-place patching config-2_1.yml) Note that if the patch no longer applies toconfig-2_1.ymla new patch file is needed, do this by manually makingconfig-2_1.ymlhigh 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 - remove the temporary patched HIGHRES file:
rm config-2_1.yml.HIGHRES - add the Apache license header to the newly created HIGHRES file:
cat license.yml config.yml.HIGHRES > config.yml.HIGHRES.new && mv config.yml.HIGHRES.new config.yml.HIGHRES - repeat the last steps to generate the MIDRES file:
patch -o config-2_1.yml.MIDRES config-2_1.yml config-2_1.yml.mid_res.patch circleci config process config-2_1.yml.MIDRES > config.yml.MIDRES rm config-2_1.yml.MIDRES cat license.yml config.yml.MIDRES > config.yml.MIDRES.new && mv config.yml.MIDRES.new config.yml.MIDRES