mirror of
https://github.com/bitcoin/bitcoin.git
synced 2025-03-05 14:06:27 -05:00
f668a3a859
fad1c55301lint: Skip COMMIT_RANGE if no CIRRUS_PR (MarcoFalke) Pull request description: Identical commit from https://github.com/bitcoin/bitcoin/pull/26588 Untested, but this may fix the red-ness in https://cirrus-ci.com/github/bitcoin/bitcoin/24.x, e.g. https://cirrus-ci.com/task/4697153604419584: Backport requested in https://github.com/bitcoin/bitcoin/pull/26588#issuecomment-1328916876 ACKs for top commit: hebasto: ACKfad1c55301, the same commit as in #26588. Tree-SHA512: 8d8a735e25bc1f774f8cbf058b95b7019941138ab78fb7819852755c7a416a783ee116457b97031d447639002353d7bf12ee8445275b7b5eec4abc7421cc171d
43 lines
1.7 KiB
Bash
Executable file
43 lines
1.7 KiB
Bash
Executable file
#!/usr/bin/env bash
|
|
#
|
|
# Copyright (c) 2018-2021 The Bitcoin Core developers
|
|
# Distributed under the MIT software license, see the accompanying
|
|
# file COPYING or http://www.opensource.org/licenses/mit-license.php.
|
|
|
|
export LC_ALL=C
|
|
|
|
GIT_HEAD=$(git rev-parse HEAD)
|
|
if [ -n "$CIRRUS_PR" ]; then
|
|
COMMIT_RANGE="${CIRRUS_BASE_SHA}..$GIT_HEAD"
|
|
echo
|
|
git log --no-merges --oneline "$COMMIT_RANGE"
|
|
echo
|
|
test/lint/commit-script-check.sh "$COMMIT_RANGE"
|
|
else
|
|
COMMIT_RANGE="SKIP_EMPTY_NOT_A_PR"
|
|
fi
|
|
export COMMIT_RANGE
|
|
|
|
# This only checks that the trees are pure subtrees, it is not doing a full
|
|
# check with -r to not have to fetch all the remotes.
|
|
test/lint/git-subtree-check.sh src/crypto/ctaes
|
|
test/lint/git-subtree-check.sh src/secp256k1
|
|
test/lint/git-subtree-check.sh src/minisketch
|
|
test/lint/git-subtree-check.sh src/leveldb
|
|
test/lint/git-subtree-check.sh src/crc32c
|
|
test/lint/check-doc.py
|
|
test/lint/all-lint.py
|
|
|
|
if [ "$CIRRUS_REPO_FULL_NAME" = "bitcoin/bitcoin" ] && [ "$CIRRUS_PR" = "" ] ; then
|
|
# Sanity check only the last few commits to get notified of missing sigs,
|
|
# missing keys, or expired keys. Usually there is only one new merge commit
|
|
# per push on the master branch and a few commits on release branches, so
|
|
# sanity checking only a few (10) commits seems sufficient and cheap.
|
|
git log HEAD~10 -1 --format='%H' > ./contrib/verify-commits/trusted-sha512-root-commit
|
|
git log HEAD~10 -1 --format='%H' > ./contrib/verify-commits/trusted-git-root
|
|
mapfile -t KEYS < contrib/verify-commits/trusted-keys
|
|
git config user.email "ci@ci.ci"
|
|
git config user.name "ci"
|
|
${CI_RETRY_EXE} gpg --keyserver hkps://keys.openpgp.org --recv-keys "${KEYS[@]}" &&
|
|
./contrib/verify-commits/verify-commits.py;
|
|
fi
|