In the 1.4.4 release we are starting to merge non-XML files into a build
folder :-) We are using this functionality for the NDepend task, and in
1.5.0 this is being expanded to even more tasks (e.g. NCover, expanded file
merge options, etc.)

The build folder is (artefact folder)\(label)[\(task name)]. If the artefact
folder is not defined in the project definition, then this defaults to
(project name)\Artifacts, and I think it is stored under the current
directory. The label comes from whichever labeller is configured for the
project - by default this will increment an integer every build.

To access this files from the dashboard, there is a new action under
projects to allow downloading files:
http://(server)/(ccnet)/server/(servername)/project/(projectname)/RetrieveFi
le.aspx?file=(taskname)/(filename)&label=(label). 

The bad news, there is an issue with this on Win2K8 servers - it appears
that IPSec is killing the file transfer process :-( We are looking into
this, but haven't figured out how to fix it (yet).



Craig

-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of CinnamonDonkey
Sent: Saturday, 13 June 2009 12:54 a.m.
To: ccnet-user
Subject: [ccnet-user] Saving artifact files with a build


Hi All,

As part of my latest CC.NET adventure I have a build project which
results in several artifact files of varying formats (*.pdf, *.pdb for
example).

I'd like to have these collated and accessable from the project build
report page.

It would be nice if each build had it's own folder in which build
artifacts could be stored. It should then be possible to  reference
the contents of this folder from within XSL to add links so that the
artifacts can be downloaded on the report page.

Since CC.Net dosn't currently handle this. I'm experimenting to find a
work around. I have tried creating a folder in the "artifacts
\buildlogs" folder and placing some files inside of there. Then in my
XSL template I am then trying to create a "right click and save as"
type link for retrieving the file. But I can't seem to get the path
right.

Any idea what the path should look like?

Cheers,
Shaun


p.s. I second the comment at the bottom of the "Merge Publisher"
page...
http://confluence.public.thoughtworks.org/display/CCNET/File+Merge+Task


Reply via email to