Note that there are some explanatory texts on larger screens.

plurals
  1. POCruiseControl.Net build logs not showing on CCNet website after upgrade
    primarykey
    data
    text
    <p>We've been using CruiseControl.Net for a couple of years now and it has been working fine. However, since our last upgrade a few weeks ago to the latest version (1.5.0.6237) our build reports are failing to display on the ccnet website. Instead we get the following message:</p> <blockquote> <pre><code>"BUILD FAILED Project: TX Date of build: 2010-06-22 23:41:54 Running time: 00:05:06 Integration Request: Build (ForceBuild) triggered from ScheduleTrigger Last changed: 2010-06-22 15:14:14 Last log entry: Merge Branches: Origin=$/Source/RE/Branches/3.1 Version: 2629 [DT- 3652]: Reporting: Capture tradable duration seperately Modifications since last build (10) Checked in Donald.sutherland Trunk/SLP/SLPDatabase/CreateScripts/CreateReportDataStoreTables.sql Merge Branches: Origin=$/Source/RE/Branches/3.1 Version: 2629 [DT-3652]: Reporting: Capture tradable duration seperately 2010-06-22 15:14:14 Checked in Donald.sutherland Trunk/SLP/SLPDatabase/Change Scripts/ReportDataStore/RpDataStoreDatabaseChangeScript.sql Merge Branches: Origin=$/Source/RE/Branches/3.1 Version: 2629 [DT-3652]: Reporting: Capture tradable duration seperate </code></pre> </blockquote> <p>What should follow is a number of error messsages indicating why the build has failed. The webpage that is failing to parse the log file is "ViewBuildReport.aspx". In order to get an explanation, our development team has to go through the full Build Log xml and search for failures.</p> <p>The build.config file is attached below:</p> <pre><code>&lt;project name="TX" queue="Build" queuePriority="1400"&gt; &lt;triggers&gt; &lt;scheduleTrigger time="21:00" buildCondition="ForceBuild"&gt; &lt;weekDays&gt; &lt;weekDay&gt;Monday&lt;/weekDay&gt; &lt;weekDay&gt;Tuesday&lt;/weekDay&gt; &lt;weekDay&gt;Wednesday&lt;/weekDay&gt; &lt;weekDay&gt;Thursday&lt;/weekDay&gt; &lt;weekDay&gt;Friday&lt;/weekDay&gt; &lt;weekDay&gt;Saturday&lt;/weekDay&gt; &lt;weekDay&gt;Sunday&lt;/weekDay&gt; &lt;/weekDays&gt; &lt;/scheduleTrigger&gt; &lt;/triggers&gt; &lt;sourcecontrol type="vault" autoGetSource="true" applyLabel="false"&gt; &lt;executable&gt;c:\program files\sourcegear\vault client\vault.exe&lt;/executable&gt; &lt;username&gt;build&lt;/username&gt; &lt;password&gt;*********&lt;/password&gt; &lt;host&gt;niddrie.dataexplorers.net:8080&lt;/host&gt; &lt;repository&gt;DXL Source&lt;/repository&gt; &lt;folder&gt;$/Source/TX/Trunk&lt;/folder&gt; &lt;ssl&gt;false&lt;/ssl&gt; &lt;useWorkingDirectory&gt;true&lt;/useWorkingDirectory&gt; &lt;workingDirectory&gt;D:\Projects\Source\TX\Trunk&lt;/workingDirectory&gt; &lt;cleanCopy&gt;true&lt;/cleanCopy&gt; &lt;timeout units="minutes"&gt;30&lt;/timeout&gt; &lt;/sourcecontrol&gt; &lt;tasks&gt; &lt;msbuild&gt; &lt;executable&gt;C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe&lt;/executable&gt; &lt;workingDirectory&gt;D:\Projects\Source\TX\Trunk&lt;/workingDirectory&gt; &lt;projectFile&gt;TransactionExplorer.sln&lt;/projectFile&gt; &lt;buildArgs&gt;/noconsolelogger /p:Configuration=Release /v:diag&lt;/buildArgs&gt; &lt;targets&gt;Build&lt;/targets&gt; &lt;timeout&gt;600&lt;/timeout&gt; &lt;logger&gt;C:\Program Files\CruiseControl.NET\server\ThoughtWorks.CruiseControl.MSBuild.dll&lt;/logger&gt; &lt;/msbuild&gt; &lt;exec&gt; &lt;executable&gt;deploy.bat&lt;/executable&gt; &lt;baseDirectory&gt;D:\Projects\Source\TX\Trunk&lt;/baseDirectory&gt; &lt;buildArgs&gt;D:\Projects\Source\TX\Trunk D:\MasterWebsite\SfsWebroot\Autobuild\TX&lt;/buildArgs&gt; &lt;buildTimeoutSeconds&gt;500&lt;/buildTimeoutSeconds&gt; &lt;/exec&gt; &lt;/tasks&gt; &lt;publishers&gt; &lt;!-- Mandatory, config file does not work without --&gt; &lt;xmllogger logDir="C:\Program Files\CruiseControl.NET\server\TX\Artifacts\buildlogs" /&gt; &amp;email; &lt;/publishers&gt; &lt;/project&gt; </code></pre> <p>As you can see, there is a publisher and the config file hasn't changed since we upgraded to the latest CruiseControl Version. Finally, the necessary log files get generated during the build so it seems to be an issue with the xsd parse or the website itself? The build result files generated are listed below:</p> <ol> <li>C:\Program Files\CruiseControl.NET\server\TX\Artifacts\msbuild-results.xml</li> <li>C:\Program Files\CruiseControl.NET\server\TX\Artifacts\buildlogs\log20100622234154.xml</li> </ol> <p>Any help to get this working will be greatly appreciated.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload