KUBERNETES_MEMORY_LIMIT: 4Gi
script:
# TODO (issue #3272) `master` is not appropriate for use on release-xxxx branches, how should we handle that?
- # See discussion at https://gitlab.com/gromacs/gromacs/-/merge_requests/67
- REV=$(git fetch -q https://gitlab.com/gromacs/gromacs.git master && git show -s --pretty=format:"%h" `git merge-base --fork-point FETCH_HEAD HEAD`)
- RUN_CLANG_TIDY=run-clang-tidy-$COMPILER_MAJOR_VERSION bash admin/clang-tidy.sh check --parallel=$KUBERNETES_CPU_LIMIT --warnings=clang-tidy.log --rev=$REV -B=$BUILD_DIR
- grep -iq "found code issues" clang-tidy.log | tee code-lint.txt || true
KUBERNETES_MEMORY_LIMIT: 2Gi
EXTRA_INSTALLS: clang-format-$COMPILER_MAJOR_VERSION
script:
- - export CLANG_FORMAT=clang-format-$COMPILER_MAJOR_VERSION
- - admin/clang-format.sh check --rev=HEAD^ --warnings=clang-format.log
+ # TODO (issue #3272) `master` is not appropriate for use on release-xxxx branches, how should we handle that?
+ - REV=$(git fetch -q https://gitlab.com/gromacs/gromacs.git master && git show -s --pretty=format:"%h" `git merge-base FETCH_HEAD HEAD`)
+ - CLANG_FORMAT=clang-format-$COMPILER_MAJOR_VERSION admin/clang-format.sh check --rev=$REV --warnings=clang-format.log
- grep -iq "needs formatting" clang-format.log | tee formatting.txt || true
- if [ -s formatting.txt ] ; then echo "clang-format.sh found issues"; exit 1; fi
artifacts:
KUBERNETES_CPU_REQUEST: 1
KUBERNETES_MEMORY_LIMIT: 2Gi
script:
- - admin/copyright.sh check --rev=HEAD^ --warnings=copyright.log
+ # TODO (issue #3272) `master` is not appropriate for use on release-xxxx branches, how should we handle that?
+ - REV=$(git fetch -q https://gitlab.com/gromacs/gromacs.git master && git show -s --pretty=format:"%h" `git merge-base FETCH_HEAD HEAD`)
+ - admin/copyright.sh check --rev=$REV --warnings=copyright.log
- grep -iq "copyright year" copyright.log | tee years.log || true
- grep -iq "copyright header" copyright.log | tee headers.log || true
- if [[ -s years.log || -s headers.log ]] ; then