Store logs of build container after builds #88
Labels
No Label
Roadmap
V
bug
docs
duplicate
enhancement
good first issue
help wanted
idea
invalid
question
wontfix
Idea
Roadmap
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vieter-v/vieter#88
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
The absolute minimum we could do to make the builds somewhat debugeable is to store the logs of each run of the build container, so admins can check these logs in case a package failed to build.
To keep things centralized, we could add a route
/pkgname-pkgver-pkgrel-arch/logs
, to which we can POST the logs of a build for that package. This would keep the logs stored at the Vieter server, making sure the cron container doesn't need to store anything.