ment (Yep, we've got NUnit and NDoc in there alongside NAnt...we
re-link its tasks against the latest versions). The only thing anybody
needs in order to build (including the build server) is SVN access and
the framework SDK. It's entirely self-contained, and we like that.
*Kudos to a
ntally. For automatic, yet
cautious, releases, deploy through the build server.
I think I've seen this kicked around over on the developer list; I
apologise if this would have been more appropriate there. My rationale
for posting it here is, well, I'm a user, not a developer. =)
Regards,
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
warrior has been wishing for a /list switch for the
Draco client for a while now because he can't remember the correct name
or case for all of his nearly 150 builds now...]
> -Original Message-
> From: [EMAIL PROTECTED]
[mailto:draconet-users-
> [EMAIL PROTECTED] On B
