Bug 1344191

Summary:	RFE: let's have separate webhooks for each package in copr
Product:	[Community] Copr	Reporter:	Pavel Raiskup <praiskup>
Component:	frontend	Assignee:	Copr Team <copr-team>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	jkadlcik
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-04-03 18:31:45 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Pavel Raiskup 2016-06-09 06:08:47 UTC

ATM, webhook in Copr triggers build of all packages that are configured to be
built by webhook.  Because different package might come from different source
repositories, it is at least wasting of resources to spin the builds for all
packages when only one of them was changed;  but it also very likely will
break the repository.

Comment 1 clime 2016-06-13 05:08:47 UTC

Good point!

Comment 2 Pavel Raiskup 2017-12-15 09:03:40 UTC

(In reply to Pavel Raiskup from comment #0)
> Because different package might come from different source repositories, it
> is at least wasting of resources

Seems like there's some work-around for this trying to match source repository
where the webhook comes from with the "SCM's git repo" url.  This is however
rather non-flexible - giving the CI work-flow artificial limits.  Eg:

Per https://docs.pagure.org/copr.copr/webhook_hacking.html#webhook-hacking

The payload dict requested ^^ is just pain, one would like to do just
'curl https://copr.fedorainfracloud.org/webhooks/github/16322/0bdb2d04-30f5-41d5-8e9d-da27c38ef426/' and that's it.


Per https://docs.pagure.org/copr.copr/user_documentation.html
> The only source type which make sense together with webhooks is “SCM”.

Meh, this is rather ugly limitation :(.  The CI (e.g. some Jenkins jobs)
can create the tarball + spec => and srpm, and provide that srpm on some
public url (so srpm-url method might succeed).

Comment 3 Jakub Kadlčík 2023-04-03 18:31:45 UTC

The bugs related to Copr build system are now migrated to the
default Copr team tracker:
https://github.com/fedora-copr/copr/issues/2640