You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a build is triggered by webhook, we don't set the "build by" field nor display any information about the webhook. People then ask what and why submitted the build.
Are we able to store the webhook payload or just parse some information from it and link it in the build info page?
Btw., custom webhook content is stored in result dir on backend. The only
thing I'm not sure about is the security perspective (can webhooks contain
some private data?). If this isn't safe to make public, we have to store
the webook in Frontend "build_private" table (temporarily, since it is a
lot of data).
The text was updated successfully, but these errors were encountered:
Triage time: @FrostyX wants at least basic info about the build, like "This has been submitted by webhook".
Then there's issue #304 that we could combine this with.
Original issue: https://pagure.io/copr/copr/issue/634
Opened: 2019-04-03 20:14:03
Opened by: frostyx
When a build is triggered by webhook, we don't set the "build by" field nor display any information about the webhook. People then ask what and why submitted the build.
Are we able to store the webhook payload or just parse some information from it and link it in the build info page?
praiskup commented at 2019-04-04 05:22:48:
This probably isn't good for build scheduler ... hmm.
+1 for the hook payload backup somewhere, discussed also here https://pagure.io/copr/copr/issue/628#comment-564135
praiskup commented at 2020-06-22 10:58:28:
Btw., custom webhook content is stored in result dir on backend. The only
thing I'm not sure about is the security perspective (can webhooks contain
some private data?). If this isn't safe to make public, we have to store
the webook in Frontend "build_private" table (temporarily, since it is a
lot of data).
The text was updated successfully, but these errors were encountered: