search

fedora-copr / copr

RPM build system - upstream for https://copr.fedorainfracloud.org/
114 stars 62 forks source link

Better overview of actions being run, statues, etc. #1108

Open fedora-copr-github-bot opened 1 year ago

fedora-copr-github-bot commented 1 year ago

Original issue: https://pagure.io/copr/copr/issue/1108 Opened: 2019-11-18 11:07:42 Opened by: frostyx

This RFE is based on discussion from PR#663

An action can fail and result in ActionResult.FAILURE. In this case, the status is stored into the database and that's that. This may be sufficient for some actions (maybe?), but it is a problem when a user is depending on that action. For example #652, where a user wanted to fork a project, it failed because of generating a new GPG key and then nothing got forked ... and the user had no way of finding out what is going on.

We should handle these situations differently. A possible solution is described by @praiskup in 663#comment-83629.

praiskup commented 1 year ago

Triage time: we have #304 requesting a page for webhooks history; it would be nice to have a page for actions history.

praiskup commented 1 year ago

Triage time: It would be nice to see the action log files in the web-UI somewhere.

praiskup commented 1 year ago

Triage time: in #1017 we discussed that actions are actually not assigned to a concrete Copr.id - so it is not easy to tell copr-related actions...