Bug 1332438

Summary:	[RFE] backend: internal message bus support
Product:	[Internal] Red Hat Internal Copr	Reporter:	Jakub Filak <jfilak>
Component:	backend	Assignee:	Pavel Raiskup <praiskup>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	gallen, jberan
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-09-18 09:10:42 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:

Description Jakub Filak 2016-05-03 08:13:52 UTC

Description of problem:
Fedora instance of COPR notifies users about a build status through fedmsg. It would be nice if Internal COPR could notify users via any possible channel - e-mail preferably.

I want to run "copr-cli build --nowait" from a Jenkins job and I want to get a notification when the build is finished. If I could specify a custom e-mail address, I would be really happy.


Actual results:
No notifications at all.

Expected results:
A notification channel available.

Comment 1 Pavel Raiskup 2016-05-12 05:23:05 UTC

FTR: Michal Srb suggested to have alternative "webhook" feature, or to connect
internal copr to some message bus.

Comment 4 Pavel Raiskup 2016-12-09 17:26:14 UTC

CI bus seems to support STOMP, here is upstream PR:
https://pagure.io/copr/copr/pull-request/21

Comment 6 Pavel Raiskup 2016-12-14 21:22:34 UTC

Moving to 'backend' component.  This reflects the fact that fedora's copr
sends messages from backend too (and the fact that backend is better for
such asynchronous actions like message sending).

In the basic proposed form, 'build.start' and 'build.end' messages are
sent.

Comment 7 Pavel Raiskup 2018-09-18 09:10:42 UTC

This has been deployed to production.