Ruben, I think I misread the documentation.
My build actually places the output of NUnit/NCover etc in the artifacts folder. I updated the config file to now explicity mention those files. You are right - there was no need to mention build output that CC.Net automatically uses in the merge task. Thanks again for helping me Ruben. Question - is there any issue placing the 3rd party software output (i.e. NUnit) in the artifact directory directly - or should I utilize the merge task to handle this? Thanks, - Ron On Feb 13, 2:13 pm, Ruben Willems <[email protected]> wrote: > Hi > > you must not merge any file from the artifacts folder, > these are buildlogs, so one can get detailed information from a build. > > if D:\CruiseControl.Net\ProjectName\Artifacts is the same as the artifact > folder > you defined in the CCNet project, I would advise you to remove it. > > Also, why do you merge csv files, is there a reason for it? > > with kind regards > Ruben Willems > > On Fri, Feb 13, 2009 at 8:08 PM, rifferte <[email protected]> wrote: > > > Yes. It looks something like this: > > > <merge> > > <files> > > <string>D:\CruiseControl.Net\ProjectName\Artifacts\*.xml</ > > string> > > <string>D:\CruiseControl.Net\ProjectName\Artifacts\*.csv</ > > string> > > </files> > > </merge> > > > Would it be the "*"? I would hope not because it would be a bit of a > > pain to have to hardcode each xml output file. > > > - Ron > > > On Feb 13, 2:06 pm, Ruben Willems <[email protected]> wrote: > > > Hi > > > > are you using a file merge task? > > > > with kind regards > > > Ruben Willems > > > > On Fri, Feb 13, 2009 at 5:30 PM, rifferte <[email protected]> wrote: > > > > > I am running into a bit of a weird issue with CCNet's Build Log and a > > > > project I am working on. > > > > > The project is configured in ccnet.config to run an msbuild project in > > > > it's prebuild task as well as run an msbuild file in it tasks like so: > > > > > <prebuild> > > > > <msbuild> > > > > ... > > > > </msbuild> > > > > </prebuild> > > > > > <tasks> > > > > <msbuild> > > > > ... > > > > </msbuild> > > > > </tasks> > > > > > Now - the project works without issue. What I am seeing though, is > > > > that if I look into the build log for a given build, it appends the > > > > prebuild msbuild log once, the tasks msbuild log file, and then the > > > > tasks msbuild log file again (albeit much lower in the file, after the > > > > list of modifications). > > > > > So - since the msbuild logs are integrated in this way, I am seeing > > > > duplicates in my web dashboard. > > > > > Does anyone have any ideas why this would happen?
