From Fedora Project Wiki
(Bugzilla Shim)
Line 11: Line 11:
  
 
Do we need a consumer for this?  There was some thought that we could just send data out on the AMQP bus about things like changing a reviews state and then this consumer would then make the change.  Is there any reason for not just having an XMLRPC call do this instead?
 
Do we need a consumer for this?  There was some thought that we could just send data out on the AMQP bus about things like changing a reviews state and then this consumer would then make the change.  Is there any reason for not just having an XMLRPC call do this instead?
 +
 +
==bugzilla-push==
 +
There is a [https://github.com/LegNeato/bugzilla-push bugzilla extension] that sends AMQP or STOMP messages on internal bugzilla events.  It looks semi-inactive.

Revision as of 19:41, 1 February 2012

Bugzilla Shim

Producer Concept

  • Bugzilla cc's bzshim@fedoraproject.org for every component in the Fedora product
  • procmail runs the message processing script i.e. no pulling.
  • Shim processes data and formats it into an AMQP message
  • Shim then sends message via a moksha producer under org.fedoraproject.bugzilla

Consumer

Do we need a consumer for this? There was some thought that we could just send data out on the AMQP bus about things like changing a reviews state and then this consumer would then make the change. Is there any reason for not just having an XMLRPC call do this instead?

bugzilla-push

There is a bugzilla extension that sends AMQP or STOMP messages on internal bugzilla events.  It looks semi-inactive.