acid: Manage persistent build logs

The output from build jobs are now stored in dedicated log files instead
of being dumped to stdout.  Files are saved in the new volume at /logs
and intended to be accessed by the web interface for auditing there.

Files are named like "X_Y_Z.log" where X = a unique build number, Y = a
timestamp in UNIX epoch seconds, and Z = the corresponding service name.

Log files are simply closed when the job is finished, so the UI can
check for the existence of a file "/logs/active" which indicates that
the highest-numbered job is still in progress.  This file is removed
afterward.

Failed jobs have a "JOB FAILED" message appended at the end of their
log.  Successful jobs simply lack this message.  One reason this is the
case is due to the build for cychedelic (--self) losing execution before
success can be affirmatively determined.

Signed-off-by: Malfurious <m@lfurio.us>

0 files changed, 0 insertions, 0 deletions