Closed Bug 711483 Opened 13 years ago Closed 13 years ago

Enable RequestWhiner extension on b.m.o.

Categories

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: gerv, Assigned: ashish)

Details

(Whiteboard: [2012q1])

The Request Whiner extension was checked in to bmo-4.0 in bug 682847. This bug requests that it be turned on. The install of the CSV template for request.cgi was successful and I've downloaded a base dataset. So now is the time to enable the extension, and try and drive some numbers down :-) Please make sure you get the latest code from the extension's bzr repo - the current code in bmo-4.0 is out of date. Remember there's a cron job to set up for bin/whineatrequests.pl. It needs to run once a week, which means that requests will be between 7 and 14 days old when they are whined about for the first time. Please let me know when it's scheduled to run so I can precede it with a blog post. (Perhaps Sunday/Monday midnight PST?) Gerv
(In reply to Gervase Markham [:gerv] from comment #0) > Please make sure you get the latest code from the extension's bzr repo - the > current code in bmo-4.0 is out of date. Can you verify this for me? I copied over bugzilla/extensions/requestwhiner/* to bmo/4.0/extensions/RequestWhiner and it didn't show any modified files. > Remember there's a cron job to set up for bin/whineatrequests.pl. It needs > to run once a week, which means that requests will be between 7 and 14 days > old when they are whined about for the first time. Please let me know when > it's scheduled to run so I can precede it with a blog post. (Perhaps > Sunday/Monday midnight PST?) Changing product to mozilla.org as this bug is more for IT to complete than the BMO developers. justdave or ashish, can one of you set up the mentioned script to run once a week along with our other BMO related cron scripts? would only need to run from one web head of course. The full path is extensions/RequestWhiner/bin/whineatrequests.pl thanks dkl
Assignee: nobody → server-ops
Component: Extensions: Other → Server Operations: Web Operations
Product: bugzilla.mozilla.org → mozilla.org
QA Contact: extensions → cshields
Version: Development → other
Sorry - it seems I hadn't checked in one update, and hadn't pushed two! That's now done; it should be revision 5 in the http://bzr.mozilla.org/bugzilla/extensions/requestwhiner/trunk/files repo. Please take this before enabling the cron job. Gerv
(In reply to Gervase Markham [:gerv] from comment #2) > Sorry - it seems I hadn't checked in one update, and hadn't pushed two! > That's now done; it should be revision 5 in the > http://bzr.mozilla.org/bugzilla/extensions/requestwhiner/trunk/files > repo. Please take this before enabling the cron job. > > Gerv Updated. Committing to: bzr+ssh://dlawrence%40mozilla.com@bzr.mozilla.org/bmo/4.0 modified extensions/RequestWhiner/bin/whineatrequests.pl modified extensions/RequestWhiner/template/en/default/requestwhiner/mail.html.tmpl modified extensions/RequestWhiner/template/en/default/requestwhiner/mail.txt.tmpl Committed revision 7990. dkl
Whiteboard: [2012q1]
dkl: when's this going to ship? It's normally every Thursday, but as it's Christmas, have you been shipping as regularly? If it has shipped, I need to chase someone to set up a cron job... Gerv
this was pushed live on dec 21.
justdave/ashish: ping? Can you please set up the cron job noted in comment #1? If you want me to open a new bug, let me know. Gerv
(In reply to Gervase Markham [:gerv] from comment #4) > dkl: when's this going to ship? It's normally every Thursday, but as it's > Christmas, have you been shipping as regularly? > > If it has shipped, I need to chase someone to set up a cron job... > > Gerv Yeah the code changes are there as glob mentioned but it is up to IT to get the scripts executing on a regular basis. The whiteboard mentiones 2012q1 so it is on there list but I am sure they will get to it as time allows. dkl
Assignee: server-ops → justdave
Assignee: justdave → jaymoz
Component: Server Operations: Web Operations → Talkback Server & Webtool
QA Contact: cshields → talkback-server
er, *what?* ok, that's just whack. stupid browser cache.
Assignee: jaymoz → ashish
Component: Talkback Server & Webtool → Server Operations: Web Operations
QA Contact: talkback-server → cshields
0 0 * * sun apache cd /data/bugzilla/www/bugzilla.mozilla.org/extensions/RequestWhiner/bin; ./whineatrequests.pl This'll run first thing Sunday morning Pacific.
(In reply to Ashish Vijayaram [:ashish] from comment #9) > 0 0 * * sun apache cd > /data/bugzilla/www/bugzilla.mozilla.org/extensions/RequestWhiner/bin; > ./whineatrequests.pl > > This'll run first thing Sunday morning Pacific. Not sure this entry will work properly as whineatrequests.pl is designed to run from the Bugzilla root directory. It may need to be changed to: 0 0 * * sun apache cd \ /data/bugzilla/www/bugzilla.mozilla.org; \ ./extensions/RequestWhiner/whineatrequests.pl dkl
This did run on Sun: Jan 15 00:00:01 mradm02 crond[12764]: (apache) CMD (cd /data/bugzilla/www/bugzilla.mozilla.org; ./extensions/RequestWhiner/bin/whineatrequests.pl)
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Did anyone actually get the mail? I have outstanding requests, and I didn't... Gerv
(In reply to Gervase Markham [:gerv] from comment #12) > Did anyone actually get the mail? I have outstanding requests, and I > didn't... nor did i.
(In reply to Ashish Vijayaram [:ashish] from comment #11) > This did run on Sun: > > Jan 15 00:00:01 mradm02 crond[12764]: (apache) CMD (cd > /data/bugzilla/www/bugzilla.mozilla.org; > ./extensions/RequestWhiner/bin/whineatrequests.pl) Is that the only output? Was there any errors in the cron log? Gerv, is there a param or other config item that may have caused the emails to not be sent? dkl
Nope; it should run unconditionally. Gerv
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.