Title: RE: [Draconet-users] Another vote for scheduled polling (and rationale).
We 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 al
Title: Message
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
Actually I like this suggestion, now that I think about it. As Yves points out, the
scheduling could get rather hairy if Draco tried to please everybody. If the cli had
a poll/force option, I think I'd be happy to schedule it as a task. Much cleaner!
Plus the service doesn't need to be resta
Isn't that more or less what the /nfb switch does in the Draco client
already? By default the client forces a build, but if you don't want it
to force and only build if "necessary" throw it the /nfb.
[This commandline warrior has been wishing for a /list switch for the
Draco client for a while no
Good point David,
I wrote that feature, and that sounds exactly like it. We wanted a nightly
build to occur only if there were changes since the last nightly build. That
is why we needed a no-force-build command line option.
I'm adamantly opposed to putting scheduling into draco.net when the
oper
