At the moment, our only forms of output are taskotron.log and stdout. So that we can better support other forms of output (HTML, smaller logs etc.), we need to have a way for tasks to save bits of output.
The simplest way to put the idea is "treat files put into a specific location during task execution as artifacts from that task which should be saved over a longer term".
In production, those task artifacts would be exposed publicly over http. The primary use case here is to allow for more detailed reports than the current text-only job-global log files allow for.
This ticket is a duplicate of https://pagure.io/taskotron/issue/78
This ticket also depends on https://pagure.io/taskotron/task-upgradepath/issue/10 This ticket also depends on https://pagure.io/taskotron/task-upgradepath/issue/9 This ticket also depends on https://pagure.io/taskotron/issue/108 This ticket also depends on https://pagure.io/taskotron/issue/91 This ticket also depends on https://pagure.io/taskotron/task-upgradepath/issue/6 This ticket also depends on https://pagure.io/taskotron/issue/80 This ticket also depends on https://pagure.io/taskotron/issue/79
This ticket had assigned some Differential requests: D406
All tasks has been resolved. Closing.
We're not done yet with this feature, created some more tasks and reopening.
This issue depended on a ticket not moved from Phabricator. T468: depcheck: create per-build and per-update artifacts
In this ticket we implemented per-build and per-update TAP results. But we still don't create per-build and per-update artifacts, which would only contain specific depcheck output for these builds/updates, in a similar fashion upgradepath implemented it in this ticket and #404.
Let's implement this. Once we have this, maintainers will be able to review output that is relevant just to their packages, instead of searching through a long log containing the whole check output.
Metadata Update from @tflink: - Issue marked as depending on: #219 - Issue marked as depending on: #220 - Issue marked as depending on: #221 - Issue marked as depending on: #222 - Issue marked as depending on: #237 - Issue marked as depending on: #246 - Issue marked as depending on: #248 - Issue marked as depending on: #251
Login to comment on this ticket.