John Hampton kirjoitti: > Eirik Schwenke wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Noah Kantrowitz skrev 26-06-2008 19:53: >> | >> | On Jun 26, 2008, at 1:50 PM, Eirik Schwenke wrote: >> |> Btw, is there a built in scheduler(aka cron) in trac ? It would certainly >> |> be nice to have this feature as part of the system, if it isn't already >> |> (eg with automatic escalation of old bugs, optional automatic transition >> |> to "won't fix" for "dead" bugs, nagging devs etc). >> | >> | As a webapp, this isn't possible. Some long-running daemon has to handle >> | timing, though Trac can handle everything else. I saw a TracCron plugin a >> | long time ago that just set things up so you ran "wget >> | http://server/trac/cron"; from cron, and it handled the scheduling and such. >> >> This seems similar to the idea coldfusion uses. > > This idea also seems kind of bad to me. "Hey, I know, let's make a > request every X (min|sec|nanosec|etc) just so I can get my web act like > cron" > > I actually think the better idea is to use cron/task scheduler for job > scheduling, since you're using it already. Either load the trac > environment and muck around with it (would require the job to be on > server) or expose an API via JSON/XMLRPC/whatever and have the script > request that. > >> I suppose this should be a ready-to-use-plugin, distributed with thin >> python-script that either implements the scheduled polling, or just the >> polling >> (for install on windows which has a ... "different" ... scheduler >> implementation ;-) > > I think that polling is a bad idea. The main reason being: Why? > >> This might be a good candidate for core? At least to the extent that this is >> relevant for workflows ? > > No, I don't think so. It doesn't really make any sense to create a > "cron" system inside trac if it depends on an external "cron" system to > trigger it.
You're vey much correct here. Trac's favourite competitor Redmine does exactly what you proposed there: It provides bunch of scripts that you can execute from cron. Be it then *nix or windows (or any other) platform. Which brings me thinking that is there way to write simple script, basically saying: "trac-run-command /my/env/path /my/command and some parameters here"? without need to write all that environment opening and such yourself. Then there should be some extensionpoint that you could write plugins specially meant for running from commandline for example to mass-post due tickets, close them or what ever you want to do. This would enable lot of more options, including expanding trac-admin command set (that I think is fixed now and can't be easily changed) -- Jani Tiainen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
