CiviCRM Community Forums (archive)

This has probably been a discussion in the past but here's the premise


CiviCRM requires a lot of cron jobs (update address, sending email, catch bounces, etc)

The nature of each cron job is very different obviously (some should be run often than others).

I was thinking instead of having a whole bunch of cron jobs, can we create a job scheduler and let it be the only cron that needs to be run?

THe scheduler cron would be run on a 5 minutes interval, but inside of the scheduler, it can lookup timestamps and determine which job needs to be fired and the interval of each individual jobs can be configured through CiviCRM,

Moreover, we can even provide a hook into the scheduler cron so developers can also add additional jobs if they wish.


Let me know what you guys think,



Chang

i have not used it, but u should check hudson: http://hudson-ci.org/

i think the unix philosophy of having one script to do one job serves a project like CiviCRM very well (IMO). We should use another open source project (like hudson or something) to do the job scheduling aspect

lobo

no idea, u might wanna do a web search. please report back your findings

lobo