On Tue, 29 Mar 2016 14:17:33 -0400
Ralph Bean <rbean(a)redhat.com> wrote:
On Thu, Mar 24, 2016 at 10:33:16AM -0400, Ralph Bean wrote:
> There's a Bugzilla outage scheduled for 00:00 2016-03-29 UTC.
> If everything goes to plan, bugzilla should start transmitting
> messages about changes to bug tickets shortly after this outage is
> complete. We have a mediator service running and ready that should
> receive those and rebroadcast them to our fedmsg bus.
> Please keep party streamers and confetti on standby.
This is all in place and working now.
As a point for discussion (maybe we can take it up in the Thursday
meeting or here on list): now that we have the data stream, what
would we like to do with it?
I know in the past we wanted it for awarding badges in badges.fp.o.
It will be useful for preparing metrics for presentations at Flock,
etc.. The fedora-packages webapp currently doesn't cache bugzilla
information because it needs a fedmsg event to invalidate the cache --
but now we have one! Same goes for fedora-hubs in the future.
What else can we come up with?
QA has been planning to rework the blockerbugs app but figured it made
more sense to wait for bugzilla-fedmsg instead of having to do things
twice. I'd really like to see the app be a bit more reactive and
event-driven instead of just syncing every X minutes.
We don't have a timeline on this right now since Taskotron is a
higher immediate priority but it's definitely on our radar.