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
Kris,
I tried that config. It failed. I switched to CVSNT for the client. Now that
I am more familiar with Draco.Net I should spend some time making it work
with cygwin's cvs port :)
If you figure it out, let me know.
- Original Message -
From: "Kris Goss" <[EMAIL PROTECTED]>
To: <[EMAIL
Title: Avoiding premature builds with CVS
It actually sleeps for a minute (the time is
configurable via the quietperiod) after it sees the first change. When it
wakes it looks to see if there were more changes, if so, the cycle is repeated.
This goes on until there are no more changes. Then t
Yes, but only if you are doing a checkout/get by tag/label. :)
In the case of a change to a version release tag/label, and the associated
get on that label, can dramatically change the source used for the build.
But I assume that right now draco doesn't support builds based on
label/tags.
It woul
