diff options
| author | Craig Jennings <c@cjennings.net> | 2026-05-19 07:33:22 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-05-19 07:33:22 -0500 |
| commit | b4c0f72235383c33d2b7ce82d8ae4e397f04a6eb (patch) | |
| tree | 9b38fd5c20fc1ededcc93cd8b73581b72a3d55aa /scripts | |
| parent | b6d737fc9e3cee641afe7b855c5356122537850b (diff) | |
| download | archangel-b4c0f72235383c33d2b7ce82d8ae4e397f04a6eb.tar.gz archangel-b4c0f72235383c33d2b7ce82d8ae4e397f04a6eb.zip | |
feat(build): save build logs to out/ alongside the ISO
Before this commit, mkarchiso's verbose output streamed to the terminal and disappeared. The cleanup trap removed work/ after each build, taking any captured output with it. Failed builds left no log to compare against past failures — including the recurring archzfs cache corruption that hits ~2 of 3 builds.
I added a tee on the mkarchiso pipeline that writes to a log file in out/. The log starts as out/build-YYYY-MM-DD-HHMM.log, pre-created and chowned to SUDO_USER. It stays user-readable even when a failed build leaves it under that name. On success, the script renames it to match the ISO's basename so finding the log for a given ISO is a one-step lookup.
set -o pipefail was already on at the top of build.sh, so mkarchiso failures still propagate through the pipe and abort the script the way they used to. No exit-code masking.
I verified the change end-to-end against a real build that hit archzfs cache corruption (log captured, kept as build-2026-05-19-0325.log, user-readable) followed by a clean retry (log renamed to archangel-2026-05-19-vmlinuz-6.18.29-lts-x86_64.log, paired with the ISO).
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions
