debian-forge-composer/cmd/osbuild-worker
Michael Vogt bc7b8355bf worker: report cashes directly to logrus
This is a bit of an RFC commit, I noticed that when we discussed
a crash from the worker we looked at individual message from
syslog/journald for the stacktrace deatils. I was wondering if
having a more direct crash report would be more useful? We can
of course also add more logrus features to flag those with tags
like "crash" or something (I did not do that in this PR, I don't
know much about the operational side, sorry).
2024-11-25 12:02:05 +01:00
..
config.go osbuild-worker: add CHANNEL to worker logs 2024-08-28 16:41:07 +02:00
config_test.go osbuild-worker: add CHANNEL to worker logs 2024-08-28 16:41:07 +02:00
export_test.go worker: report cashes directly to logrus 2024-11-25 12:02:05 +01:00
jobimpl-awsec2.go osbuild-worker: switch to aws sdk v2 for errors in ami copy jobs 2024-08-20 15:32:40 +02:00
jobimpl-container-resolve.go clienterrors: rename WorkerClientError to clienterrors.New 2024-07-31 17:04:58 +02:00
jobimpl-depsolve.go Worker/depsolve: add support for SBOM 2024-09-20 17:02:09 +02:00
jobimpl-depsolve_test.go osbuild-worker: handle error wrapping from dnfjson package 2024-09-02 14:39:03 +02:00
jobimpl-file-resolve.go clienterrors: rename WorkerClientError to clienterrors.New 2024-07-31 17:04:58 +02:00
jobimpl-koji-finalize.go Worker/koji-finalize: import uploaded SBOM documents 2024-09-20 17:02:09 +02:00
jobimpl-koji-init.go clienterrors: rename WorkerClientError to clienterrors.New 2024-07-31 17:04:58 +02:00
jobimpl-osbuild.go cmd/osbuild-worker: specify hyper v gen for azure images 2024-11-21 11:22:20 +01:00
jobimpl-osbuild_test.go osbuild-worker: tweak error to not include a \n for a failed stage 2024-07-11 09:33:40 +02:00
jobimpl-ostree-resolve.go worker: log proxy setting 2024-11-18 19:33:19 +01:00
main.go worker: report cashes directly to logrus 2024-11-25 12:02:05 +01:00
main_test.go worker: report cashes directly to logrus 2024-11-25 12:02:05 +01:00