BUG: C:\Temp\RoundhousE may not exist
ferventcoder opened this issue · comments
Writing the log file out will fail if it can't reach the folder above.
Even a bigger problem with the c:\temp\roundhouse\roundhouse.changes.log is that when RoundhousE is executed on a buildserver for multiple projects at the same time, then one of the builds fail. Because the logging file is in use by another process. A better solution would be to make the output folder required, and always log there, instead of first logging to c:\temp and then copying the file.
Yep - to do that I need to actually set up logging configuration that
explicitly points to that folder.
Rob
"Be passionate in all you do"
http://devlicio.us/blogs/rob_reynolds
http://ferventcoder.com
http://twitter.com/ferventcoder
On Thu, Jun 9, 2011 at 4:08 PM, PascalMestdach <
reply@reply.github.com>wrote:
Even a bigger problem with the c:\temp\roundhouse\roundhouse.changes.log is
that when RoundhousE is executed on a buildserver for multiple projects at
the same time, then one of the builds fail. Because the logging file is in
use by another process. A better solution would be to make the output folder
required, and always log there, instead of first logging to c:\temp and then
copying the file.Reply to this email directly or view it on GitHub:
#7 (comment)
And that would be a better solution. I am not a fan of having it go one place and then moving it somewhere. Perhaps I can grab the logger and point it to the correct directory to ease the configuration pain.
Yes, that would solve it. And maybe give the outputfolder a default to c:\temp\roundhouse so that it's no breaking change?
Actually no one knows/cares about that folder. It started as a dropping point for the log prior to moving it to the change drop folder. It was meant to be temporary at the time it was added...
Fixed in 9250541