Hi Craig
Thanks for taking the time to answer my question.
As far as I can see the problem is not that the output is published at
the wrong site (see config at the bottom). I have checked the
"Artifacts" folder to see if the output is actually copied. It is. So
I am at a loss as to find a solution to my problem.
Here is the config. The removed parts ("...") do not interact with the
output.
<project>
<askForForceBuildReason>None</askForForceBuildReason>
<category>Regressionstest</category>
<artifactDirectory />
<workingDirectory>c:\src2\baz</workingDirectory>
<externalLinks />
<initialState>Started</initialState>
<labeller type="defaultlabeller">
<incrementOnFailure>False</incrementOnFailure>
<initialBuildLabel>1</initialBuildLabel>
<labelFormat>0</labelFormat>
<postfix />
<prefix />
</labeller>
<maxSourceControlRetries>5</maxSourceControlRetries>
<modificationDelaySeconds>0</modificationDelaySeconds>
<name>baz_REG</name>
<parameters />
<prebuild>
<exec>
delete old 'bar.html'
</exec>
</prebuild>
<publishers>
<merge>
<dynamicValues />
<environment />
<files>
...
<file action="Copy">debug\server\bin\bar.html</file>
...
</files>
</merge>
<xmllogger>
<dynamicValues />
<environment />
</xmllogger>
</publishers>
<queue>main</queue>
<queuePriority>0</queuePriority>
<security type="inheritedProjectSecurity" />
<showForceBuildButton>True</showForceBuildButton>
<showStartStopButton>True</showStartStopButton>
<sourcecontrol type="nullSourceControl">
<failGetModifications>False</failGetModifications>
<failGetSource>False</failGetSource>
<failLabelSourceControl>False</failLabelSourceControl>
</sourcecontrol>
<sourceControlErrorHandling>ReportEveryFailure</
sourceControlErrorHandling>
<startupMode>UseLastState</startupMode>
<state type="state">
<directory>c:\Program Files\CruiseControl.NET\server2\</directory>
</state>
<stopProjectOnReachingMaxSourceControlRetries>False</
stopProjectOnReachingMaxSourceControlRetries>
<tasks>
...
<exec>
<buildArgs>/html:bar.html</buildArgs>
<buildTimeoutSeconds>100000</buildTimeoutSeconds>
<baseDirectory>debug\server\bin</baseDirectory>
<dynamicValues />
<environment />
<executable>foo.exe</executable>
<priority>Normal</priority>
<successExitCodes>0</successExitCodes>
</exec>
</tasks>
<triggers>
...
</triggers>
<webURL>http://IZALCO/ccnet</webURL>
</project>
Regards
Thomas
On Jun 30, 9:36 pm, "Craig & Sammi Sutherland"
<[email protected]> wrote:
> Hi Thomas
>
> This sounds like a task placement issue - in order for the report to be
> viewable it needs to be "published" to a location where CC.NET can find it
> (e.g. with a merge task or similar.)
>
> If the "publishing" task is in the tasks section after a task that has
> failed then it will not be called - so the report will not be "published".
> To ensure the report is always "published" put it into the publishers
> section instead.
>
> Craig
>
>
>
>
>
>
>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On
>
> Behalf Of Nesavi
> Sent: Thursday, 30 June 2011 6:52 p.m.
> To: ccnet-user
> Subject: [ccnet-user] htmlReportPlugin: does not show content for failed
> builds ("Unable to find file")
>
> Hi
>
> I have recently reconfigured my CCNet-configuration to use the
> "htmlReportPlugin". However, when the build fails, I cannot view the
> html-output in the dashboard. Only the error message "Unable to find file"
> is shown.
>
> This is exact opposite functionally from what I want. When a build fails, I
> need to be able to inspect the html-output, and when a build does not fail,
> I rather do not care about the html-output.
>
> Has anyone experienced anything similar?
>
> Regards
>
> Thomas
