Once bugzilla starts emitting fedmsgs, replace current sync mechanism with a consumer for those messages.
https://lists.fedoraproject.org/pipermail/qa-devel/2014-December/001051.html
Bugzilla now sends fedmsgs:
https://apps.fedoraproject.org/datagrepper/raw?topic=org.fedoraproject.prod.bugzilla.bug.new&delta=198000 https://apps.fedoraproject.org/datagrepper/raw?topic=org.fedoraproject.prod.bugzilla.bug.update&delta=198000
for the record: the bugzilla fedmsgs / fedora-messages are currently quite broken and will be until a new bugzilla2fedmsg with my recent fixes is put into production. See https://github.com/fedora-infra/bugzilla2fedmsg/pull/13 and https://github.com/fedora-infra/bugzilla2fedmsg/pull/14 .
bugzilla2fedmsg fixes are merged, but not yet in production: see https://pagure.io/fedora-infrastructure/issue/8087 .
We're still working on package reviews to get the new bugzilla2fedmsg deployable ATM.
still waiting on the new deployment. sigh.
Metadata Update from @adamwill: - Issue tagged with: enhancement
Update: the updated bugzilla2fedmsg finally got deployed, and good messages are being published now, I believe. So it should be possible to work on this now.
Unlikely to happen since Bugzilla is said to be going away, but I'll keep it here just in case.
Metadata Update from @kparal: - Custom field story_points adjusted to 8 - Issue priority set to: Low (was: Normal)
This issue has been migrated to Fedora Forge: https://forge.fedoraproject.org/quality/blockerbugs/issues/39
Please continue any further discussion there.
Log in to comment on this ticket.