Commit e3025fae authored by Cyril 'kibi' Brulebois's avatar Cyril 'kibi' Brulebois
Browse files

Release process: detect errors while generating IUKs

Without this, errors would go unreported: further steps within the for
loop would be performed, and all source versions would be attempted. If
one is lucky, a general issue (missing backslash somewhere) could easily
be spotted as it would affect all source versions. In worse cases, a
failure somewhere in the middle could go unnoticed.

Therefore: use “set -e” locally, and print an explicit error message
when any failure happens; also break out of the loop to ensure the first
issue is fixed before considering other items.
parent ce42c549
......@@ -834,6 +834,7 @@ Build the Incremental Upgrade Kits locally
mkdir -p "${IUKS_DIR:?}" && \
for source_version in ${IUK_SOURCE_VERSIONS:?}; do
(set -e
squashfs_tools_version="$(dpkg-query --showformat '${Version}\n' --show squashfs-tools)"
if [ "$squashfs_tools_version" != '1:4.4-1+0.tails1' ]; then
echo "ERROR! Your squashfs-tools is not the required version, so any generated IUKs will *not* be reproducible!"
......@@ -854,6 +855,7 @@ Build the Incremental Upgrade Kits locally
--outfile \"${IUK:?}\"" && \
sudo chown "$(id --user):$(id --group)" "${IUK:?}" && \
(cd "$(dirname "${IUK:?}")" && sha256sum "${IUK:?}" >> "${IUKS_HASHES:?}")
) || { echo "ERROR: failure detected for source version: ${source_version?:}"; break; }
This command can take a long time. In parallel, while it is running,
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment