Page MenuHomePhabricator

replace bz reporter db scraping with API queries
Closed, DeclinedPublic

Description

moving from an RT ticket over to Bugzilla itself, after talking to Andre about it:


replace bz reporter db scraping with API queries, originally RT #2577

Mon Mar 05 23:33:33 2012 Antoine Musso - Ticket created

There is a reporting script, probably in perl, sending out a weekly report about bugzilla activity.

The script was written by Tomasz Finc back in 2008.

It runs on kaulen.

Output is sent on mondays at 3am UTC.

Would be great to have the script moved to puppet and the cron puppetized.

update by Daniel:

meanwhile it is indeed puppetized and part of the bugzilla puppet module,
it also doesn't run on kaulen anymore, but on zirconium, so that has been resolved.

but:

later on the ticket it has been said that the entire script should be replaced by something that asks the API. using the current puppet code you could just change the script name, and you'll still get the cronjobs etc from puppet.

so if anyone feels a need to replace the working script, then write a new one that outputs the same result but just asks the API


Version: wmf-deployment
Severity: enhancement

Details

Reference
bz61294

Event Timeline

bzimport raised the priority of this task from to Lowest.Nov 22 2014, 3:06 AM
bzimport set Reference to bz61294.
bzimport added a subscriber: Unknown Object (MLST).

For those willing to work on this:

The file is in https://git.wikimedia.org/blob/operations%2Fpuppet.git/43973739a2c728a30fdc1e4aa4303445e72c96da/templates%2Fmisc%2Fbugzilla_report.php

The API reference is here:
http://www.bugzilla.org/docs/4.4/en/html/api/index.html

(I would love to replace 43973739a2c728a30fdc1e4aa4303445e72c96da by HEAD as in other repos so you'd see the latest version, but operations is... different.)

by now it makes probably more sense to look at a replacement for bz reporter that runs on phabricator

new ticket for that and close here?

Setting lowest priority (because I won't stop anybody from working on this but won't do it).
I don't know if we want the same thingy for Phabricator. Creating awareness of what's going on in a task tracker to a broader audience can be helpful, but the current format and content does not make me believe that it's interesting to more than a bunch of statistic lovers.

agree, i would also be fine with won't fix actually.

Wikimedia has migrated from Bugzilla to Phabricator. Learn more about it here: https://www.mediawiki.org/wiki/Phabricator/versus_Bugzilla - This task does not make sense anymore in the concept of Phabricator, hence closing as declined.