Closed Bug 952880 Opened 11 years ago Closed 11 years ago

Deploy production change notification system

Categories

(bugzilla.mozilla.org Graveyard :: Bugzilla Change Notification System, defect, P1)

Production
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mcote, Unassigned)

References

Details

(Keywords: bmo-goal)

I've verified that the Bugzilla Change Notification System (https://wiki.mozilla.org/BMO/ChangeNotificationSystem) is working well on bugzilla-dev. Next quarter I'd like to deploy a production version. This is a tracking bug for the individual steps required. It should be done in the following order, so I will only create bugs as the previous is finished to minimize confusion: * Deploy bugzfeed WebSocket server. ** Since the pulse shim is running on bugzilla-dev right now, we can immediately test that it is working. * Disable the pulse shim and ZPushNotify extension on bugzilla-dev. ** We may want to later re-enable it but ensure that it's writing to its own exchange. May not be worth the effort. * Deploy pulse shim to production. * Enable ZPushNotify extension on production. ** This needs to be last so the table doesn't fill up, since the shim deletes entries as it goes.
Depends on: 952881
Keywords: bmo-goal
Priority: -- → P1
We'll deploy it to push1.bugs.scl3.mozilla.com and push1.bugs.phx.mozilla.com.
Depends on: 987302
The system is all set up! The WebSocket server ("bugzfeed") is running on ws://bugzfeed.mozilla.org/. There is a simple example app that uses the production bugzfeed and bugzilla instances at http://people.mozilla.com/~mcote/bugzfeed_example/. I'll be blogging about the system this week.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Awesome!
Product: bugzilla.mozilla.org → bugzilla.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.