Hi Ruben, I'm currently just using the output parameter of the <exec> task;
<exec program="publish.bat" output="publish_output.txt" append="true" / > I'll pull this out and update the xcopy command in the script file instead. Cheers Dave On Aug 10, 11:34 am, Ruben Willems <[email protected]> wrote: > Hi > > how did you redirected to a file? > > like this : > > mycopy.cmd >log.txt > > try using this > mycopy.cmd >log.txt 2>&1 > > this will redirect the errorstream to standard out > hope this will give extra information > > with kind regards > Ruben Willems > > On Mon, Aug 10, 2009 at 11:52 AM, Dave Carson <[email protected]>wrote: > > > > > Well I'm still not much further on with this issue apeart from knowing > > exactly when in the build process it is occuring. > > > Basically the MSBuild part of the process does complete successfully > > but then it attempts to copy the resulting output (this is a web > > application) to a shared directory on another server. This makes the > > latest build available to our test department. > > > The copy is performed via xcopy within a batch file which is triggered > > using an <exec> task. I have configured the task to output to a text > > file and hoped to see a prompt for input from the user, thus helping > > me trace the problem. However, all I got was a list of files being > > copied which stopped part way through - no prompts, no messages - > > nothing. > > > I'm convinced that this is because the system is waiting for a prompt > > from the user but until I can get sight of it I can't work out how to > > fix the problem. > > > Any Idea..? > > > Thanks in Advance > > Dave > > > On Jul 3, 10:28 am, Dave Carson <[email protected]> wrote: > > > Hi Ruben, > > > > I've sent the log file directly to you as suggested. > > > > As and when we get to the bottom of this I'll update this thread > > > incase others have the same problem in the future. > > > > Cheers > > > > Dave > > > > On Jul 3, 10:12 am, Ruben Willems <[email protected]> wrote: > > > > > Hi > > > > > in the build log file should be the nant output, > > > > it is not visible in the dashboard maybe, but in a text/xml editor you > > > > should be able to see it. > > > > > can you mail a build log file with such a time out to me? > > > > you may do it to me personally if you do not want it to appear on the > > list > > > > > with kind regards > > > > Ruben Willems > > > > > On Fri, Jul 3, 2009 at 11:03 AM, DilbertDave <[email protected]> > > wrote: > > > > > > I have a project in CCNet (1.4.4.83) which has been build happily for > > > > > some time - until recently that is. > > > > > > For some reason it is now failing witha nAnt timeout exception > > during > > > > > the Nightly build - but not every time! > > > > > > The main problem is that the logs are incomplete so i cannot tell > > what > > > > > has gone wrong. > > > > > > All I get is: > > > > > ========================================= > > > > > Buildfile: file:///E:/[path]/prebuild.build > > > > > Target framework: Microsoft .NET Framework 2.0 > > > > > Target(s) specified: StartPreBuild > > > > > [script] Scanning assembly "l8swjzzy" for extensions. > > > > > [script] Scanning assembly "e5lqekig" for extensions. > > > > > [script] Scanning assembly "64nkcjgh" for extensions. > > > > > > StartPreBuild: > > > > > ========================================= > > > > > and that's it! > > > > > > Now I know that it gets past the PreBuild stage because other scripts > > > > > perform SVN commits and these all show up in the repository. I've > > > > > checked the msbuild_report.xml in the artifacts folder and it appears > > > > > to be complete and contains nothing to indicate a failure. > > > > > > Finally I have checked the ccnet.log files (set to record ERROR > > > > > messages) and again there is nothing relating to this build. > > > > > > Where else can I look and what can I try..? > > > > > > Thanks in advance- Hide quoted text - > > > > > - Show quoted text -
