I like
to keep complexity out of things when I can get away with it. It sounds to me
like if the dracrocli remoting interface supported a "/poll:buildname" then the
Windows scheduler could be used. Right now dracocli can be used to start a build
anyway for those who would like to run a clean build at time X via the Windows
scheduler. Adding the /poll command would let the Windows scheduler be used to
drive the "check SCC / maybe run the build" as well. Because of .NET remoting,
the scheduler and dracocli.exe don't even have to be on the draco build machine
after all.
I
believe main advantage of using the Windows scheduler is that we get a
semi-nice GUI for editing schedules for free, and secondly no complex scheduling
code needs to be created/tested. The downside is that the schedule editor is not
an integrated part of draco, but what the heck, right now the schedule editor
GUI is notepad.exe anyway. If this was a shrink-wrap software tool I suppose
leveraging Window scheduler might seem cheesy, but I think it's perfect for
this situation.
-
Jerry
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Friday, December 12, 2003 4:11 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [Draconet-users] Another vote for scheduled polling (and rati onale).
Importance: LowWe seem to evolve from poll period to a more free form of task scheduling (e.g. Poll every Monday of the month, Poll every week on Sunday and Saturday, Poll every day at 12:00 PM, Poll every ...).
Of course, it all depends on people's individual polling requirement. If only 2 scenario's exist (namely relative and absolute (daily)), why build more than that into Draco?
