summaryrefslogtreecommitdiff
path: root/contrib/cirrus
diff options
context:
space:
mode:
authorChris Evich <cevich@redhat.com>2022-07-18 12:09:47 -0400
committerChris Evich <cevich@redhat.com>2022-07-19 09:33:48 -0400
commit7b8282c79facc64a3bd5c538e76c61d3f91c854c (patch)
treebaa6622d56e10cd1324e3a3078b0b1110d58adf2 /contrib/cirrus
parente8c5781a7c4719a5c88bb1b4bde51ca2affee244 (diff)
Cirrus: Verify expected binary artifacts present
Other CI systems depend/expect a full set of compiled binaries are included in the success task's binary artifact (zip file). However, it's possible some mistake in CI could silently lead to one or more binaries not being produced. For example, a `bin_cache` failure. Fix this by verifying all expected/required files are present. If not, print the name of the missing binary to assist in troubleshooting/debugging. Signed-off-by: Chris Evich <cevich@redhat.com>
Diffstat (limited to 'contrib/cirrus')
-rwxr-xr-xcontrib/cirrus/runner.sh2
1 files changed, 1 insertions, 1 deletions
diff --git a/contrib/cirrus/runner.sh b/contrib/cirrus/runner.sh
index 80fc01d..514b2ae 100755
--- a/contrib/cirrus/runner.sh
+++ b/contrib/cirrus/runner.sh
@@ -25,7 +25,7 @@ _run_build() {
# This will get scooped up and become part of the artifact archive.
# Identify where the binary came from to benefit downstream consumers.
- cat >> bin/aardvark-dns.info << EOF
+ cat | tee bin/aardvark-dns.info << EOF
repo: $CIRRUS_REPO_CLONE_URL
branch: $CIRRUS_BASE_BRANCH
title: $CIRRUS_CHANGE_TITLE