Bugzilla should have cron triggers at specific intervals

RESOLVED WONTFIX

Status

()

Bugzilla
Administration
P3
enhancement
RESOLVED WONTFIX
17 years ago
4 years ago

People

(Reporter: justdave, Unassigned)

Tracking

Details

Right now, the default Bugzilla installation suggests two cron jobs: 
whineatnews.pl and collectstats.pl.

There are other things in the works (password reset requests, email address 
changes, etc) that would require cron jobs due to needing to delete tokens after 
they become a certain age, and possibly emailing reminders before a token 
expires.

Instead of requesting the user add yet another cron job, why not suggest a single 
cron job which simply calls a trigger script in bugzilla, which can then do its 
own scheduling based on the time it was called?

Using this method would allow other timed tasks to be added to bugzilla and have 
them automatically work when the user updates without having to ask the user to 
install yet another cron job.
and there should, of course, be an administration interface of some sort 
(probably in params?) to let the user choose which jobs actually get run.
Severity: normal → enhancement
Priority: -- → P3
Target Milestone: --- → Bugzilla 2.18

Comment 2

17 years ago
-> Bugzilla product, Installation component (also affects Administration),
reassigning.
Assignee: tara → zach
Component: Bugzilla → Installation
Product: Webtools → Bugzilla
Version: Bugzilla 2.13 → 2.13

Comment 3

17 years ago
Unless checksetup.pl sets the cronjob, this is not installation. Over to 
administration.
Assignee: zach → justdave
Component: Installation → Administration
Enhancements which don't currently have patches on them which are targetted at
2.18 are being retargetted to 2.20 because we're about to freeze for 2.18. 
Consideration will be taken for moving items back to 2.18 on a case-by-case
basis (but is unlikely for enhancements)
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
Bugzilla 2.20 feature set is now frozen as of 15 Sept 2004.  Anything flagged
enhancement that hasn't already landed is being pushed out.  If this bug is
otherwise ready to land, we'll handle it on a case-by-case basis, please set the
blocking2.20 flag to '?' if you think it qualifies.
Target Milestone: Bugzilla 2.20 → Bugzilla 2.22
Reassigning bugs that I'm not actively working on to the default component owner
in order to try to make some sanity out of my personal buglist.  This doesn't
mean the bug isn't being dealt with, just that I'm not the one doing it.  If you
are dealing with this bug, please assign it to yourself.
Assignee: justdave → administration
QA Contact: mattyt-bugzilla → default-qa

Updated

13 years ago
Target Milestone: Bugzilla 2.22 → ---
Bugzilla now has a job queue and a way of adding things to it. I'm fairly sure you can schedule stuff for the future using the run_after key on the creation of the job.

So, whether or not we convert whineatnews.pl or collectstats.pl to use this mechanism rather than cron, we don't need our own additional cron daemon.

Gerv
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.