Bug 1332438 - [RFE] backend: internal message bus support
Summary: [RFE] backend: internal message bus support
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Internal Copr
Classification: Internal
Component: backend
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pavel Raiskup
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-03 08:13 UTC by Jakub Filak
Modified: 2018-09-18 09:10 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-09-18 09:10:42 UTC
Embargoed:


Attachments (Terms of Use)

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.


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