【问题标题】:CruiseControl.Net build logs not showing on CCNet website after upgrade升级后,CruiseControl.Net 构建日志未显示在 CCNet 网站上
【发布时间】:2011-01-13 22:35:26
【问题描述】:

我们已经使用 CruiseControl.Net 几年了,它运行良好。但是,自从几周前我们上次升级到最新版本 (1.5.0.6237) 以来,我们的构建报告无法在 ccnet 网站上显示。相反,我们收到以下消息:

"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

接下来应该是一些错误消息,指出构建失败的原因。无法解析日志文件的网页是“ViewBuildReport.aspx”。为了得到解释,我们的开发团队必须通过完整的 Build Log xml 并搜索失败。

build.config 文件附在下面:

<project name="TX" queue="Build" queuePriority="1400">
 <triggers>
  <scheduleTrigger time="21:00" buildCondition="ForceBuild">
   <weekDays>
    <weekDay>Monday</weekDay>
    <weekDay>Tuesday</weekDay>
    <weekDay>Wednesday</weekDay>
    <weekDay>Thursday</weekDay>
    <weekDay>Friday</weekDay>
    <weekDay>Saturday</weekDay>
    <weekDay>Sunday</weekDay>
   </weekDays>
  </scheduleTrigger>
 </triggers>
 <sourcecontrol type="vault" autoGetSource="true" applyLabel="false">
  <executable>c:\program files\sourcegear\vault client\vault.exe</executable>
  <username>build</username>
  <password>*********</password>
  <host>niddrie.dataexplorers.net:8080</host>
  <repository>DXL Source</repository>
  <folder>$/Source/TX/Trunk</folder>
  <ssl>false</ssl>
  <useWorkingDirectory>true</useWorkingDirectory>
  <workingDirectory>D:\Projects\Source\TX\Trunk</workingDirectory>
  <cleanCopy>true</cleanCopy>
  <timeout units="minutes">30</timeout>
 </sourcecontrol>
 <tasks>
  <msbuild>
   <executable>C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe</executable>
   <workingDirectory>D:\Projects\Source\TX\Trunk</workingDirectory>
   <projectFile>TransactionExplorer.sln</projectFile>
   <buildArgs>/noconsolelogger /p:Configuration=Release /v:diag</buildArgs>
   <targets>Build</targets>
   <timeout>600</timeout>
   <logger>C:\Program Files\CruiseControl.NET\server\ThoughtWorks.CruiseControl.MSBuild.dll</logger>
  </msbuild>
  <exec>
   <executable>deploy.bat</executable>
   <baseDirectory>D:\Projects\Source\TX\Trunk</baseDirectory>
   <buildArgs>D:\Projects\Source\TX\Trunk D:\MasterWebsite\SfsWebroot\Autobuild\TX</buildArgs>
   <buildTimeoutSeconds>500</buildTimeoutSeconds>
  </exec>
 </tasks>
 <publishers>
  <!-- Mandatory, config file does not work without -->
  <xmllogger logDir="C:\Program Files\CruiseControl.NET\server\TX\Artifacts\buildlogs" />
  &email;
 </publishers>
</project>

如您所见,自从我们升级到最新的 CruiseControl 版本以来,有一个发布者并且配置文件没有更改。最后,在构建过程中生成了必要的日志文件,所以这似乎是 xsd 解析或网站本身的问题?生成的构建结果文件如下:

  1. C:\Program Files\CruiseControl.NET\server\TX\Artifacts\msbuild-results.xml
  2. C:\Program Files\CruiseControl.NET\server\TX\Artifacts\buildlogs\log20100622234154.xml

我们将不胜感激任何帮助来完成这项工作。

【问题讨论】:

    标签: cruisecontrol.net


    【解决方案1】:

    您检查过您的电子邮件发布者吗? CCNET 1.5 发生了重大变化。你可以在这里阅读更多:

    如果我理解你的话,你说你的构建工作正常,但由于你升级它失败了,不是吗?你是怎么升级的?您是否更改了目录/权限?

    【讨论】:

    • 您好本杰明,感谢您的回复。我们最终使用了一个自定义的 xslt 来解析结果。升级似乎带有损坏的 xslt,因此我们无法清楚地查看构建结果。
    猜你喜欢
    • 2014-11-15
    • 1970-01-01
    • 2018-01-14
    • 1970-01-01
    • 2021-04-10
    • 2015-10-07
    • 1970-01-01
    • 2021-05-25
    • 2020-09-21
    相关资源
    最近更新 更多