[libre-riscv-dev] gitlab-ci-archiver status

Luke Kenneth Casson Leighton lkcl at lkcl.net
Fri Apr 10 00:19:03 BST 2020

ah i just realised, you may be tempted to assume that the outgoing command
is not 100% reliable and thus start writing retry and store and forward

this is why i said assume the UNIX philosophy do one task and do it well.

other services do store and forward so use them.

we can always install exim4 as a relay.

so on consideration please use whatever wrapper rust puts around popen2 or
popen3, shove the log out on stdout, no command options (no env vars) where
the command is from the config file, no paramers, nothing.

it then becomes a 5 minute job to write a bash script "mail -s "build log"
fred at foo"

if the command does produce stderr output shove that into the error logs
and forget about it.

we need to get this handed over to alain and frieder as soon as possible.

this or equivalent will do



crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68

More information about the libre-riscv-dev mailing list