Title: Message
|
Hi
David
Glad you like
Draco.NET. 99 builds is pretty impressive! At the moment nothing
exists to give you information about who launched the build. I'm not
knowledgeable about .NET remoting, and the developer who wrote the client is on
holiday just now - but I'm sure it would be reasonably easy to at least write
the caller's IP to the log file.
-Mark
Howdy, y'all,
My
compliments to the developers; Draco.NET is very fine product. There are
some little features that would (maybe already do) make it much more
"trustworthy" (beside remote request authentication). I've got lots of
other questions/observations/suggestions, but I'll stick to just one at a
time... ;)
I
have exactly 99 modules under CI monitoring with Draco.NET in my shop as of
this morning. That'll probably grow by a one or two a week for the
foreseeable future -- which is good. A ten-minute interval doesn't put
too much strain on VSS. However, I made the mistake of letting the
Draco.NET client "into the wild" so that developers could self-service
*immediate* build requests and
save themselves (and the analysts who're waiting to test something) 9 or so
minutes of thumb-twiddling.
The
problem now is that I don't know which loose cannon is firing off builds
willy-nilly. It's not a huge problem, but I can see it getting
irritating over the next quarter as we add more and more staff.
:|
Is
there already some switch (that I don't see) in the config for at least
putting the IP address of the remote requester in the build report? (If
not, I'll climb into the source when it really starts to get under my skin.
:)
|
