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.
Good point!
(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).
The bugs related to Copr build system are now migrated to the default Copr team tracker: https://github.com/fedora-copr/copr/issues/2640