What the developer wrote
Authored by fanquake
ci: detect apk usage generally
Rather than listing image names, which makes it less easy to
run custom CI jobs.
What changed, and why it matters
This is a tiny change to Bitcoin Core's internal continuous integration (CI) setup script. It switches from checking whether the Docker image name contains 'alpine' to checking whether the 'apk' package manager command is available. This makes the CI script more flexible for custom images but does not change any user-facing behavior, network rules, or security-sensitive logic.
No security action required. This is a benign CI refactoring change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
In ci/test/01_base_install.sh, the condition for running Alpine package installation was changed from a string match on CI_IMAGE_NAME_TAG to a direct check for the apk binary via ‘command -v apk’. This is a maintainability/refactoring change in the CI infrastructure only. It does not alter package lists, permissions, cryptographic checks, or runtime behavior of the Bitcoin Core software.
Changed components
ci/test/01_base_install.shInspect captured patch +1 / −1
diff --git a/ci/test/01_base_install.sh b/ci/test/01_base_install.sh
index 3e0bc466..d62221a7 100755
--- a/ci/test/01_base_install.sh
+++ b/ci/test/01_base_install.sh
@@ -37,7 +37,7 @@ if [ -n "${APT_LLVM_V}" ]; then
)
fi
-if [[ $CI_IMAGE_NAME_TAG == *alpine* ]]; then
+if command -v apk >/dev/null 2>&1; then
${CI_RETRY_EXE} apk update
# shellcheck disable=SC2086
${CI_RETRY_EXE} apk add --no-cache $CI_BASE_PACKAGES $PACKAGES
Why this scored 17/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.