Bug 1526337 - RFE: CI: webhook_*_push should return the allocated build-id(s)
Summary: RFE: CI: webhook_*_push should return the allocated build-id(s)
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Copr
Classification: Community
Component: frontend
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Copr Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-15 09:18 UTC by Pavel Raiskup
Modified: 2023-04-03 14:47 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-04-03 14:47:07 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1344191 0 unspecified CLOSED RFE: let's have separate webhooks for each package in copr 2023-04-03 18:31:44 UTC

Internal Links: 1344191

Description Pavel Raiskup 2017-12-15 09:18:29 UTC
This is needed for e.g. hooking the copr's webhook feature into Travis
build in github.  Use-case:

Some upstreams (notable example pgjdbc) want to have the copr build
(with build-time tests) done for each pull-request, and block the
PR unless the RPM build succeeds.  It is now non-trivial to get the
final build-status from copr, because the webhook call doesn't return
the build-id.

I'm not sure the actual webhooks have to be necessarily changed, and
return all the submitted build-ids (several builds might be triggered
by one webhook call);  we might as well implement bug 1344191 on
say /webhooks/package/<copr_id>/<package_name/<uuid>/ url -- and
add the allocated build-id into the response JSON.

As a followup feature, we could have:
$ copr-webhook --project <COPR_ID> \
               --package <PACKAGE_NAME> \
               --uuid-token <SECRET>
.. which would be able to parse the response.

Comment 1 Pavel Raiskup 2023-04-03 14:47:07 UTC
The bugs related to Copr build system are now migrated to the
default Copr team tracker:
https://github.com/fedora-copr/copr/issues/2633


Note You need to log in before you can comment on or make changes to this bug.