如何巡航控制.NET应用构建/测试工具？ [英] How does Cruise Control .NET use build / test tools?

问题描述

我是相当新的CC .NET但在不同的环境中使用其他构建工具（而不是C＃）previously。

I am fairly new to CC .NET but have used other build tools in different environments (not C#) previously.

我的问题是，当我选择楠作为构建工具（构建脚本）及NUnit的作为测试工具（测试）确实CC .NET运行这些工具的参数从命令行我在配置文件中指定？

My question is, when I choose NAnt as a Build Tool (for build scripts) & NUnit as a Test Tool (for testing) does CC .NET execute the command line for these tools with the parameters I specify in the config file?

例如我已经南特安装我的构建脚本，将CC .NET中的恶性目录，以建立一个项目执行NAnt.exe还是它的其他手段？

For example I have NAnt installed for my build scripts, will CC .NET execute NAnt.exe in the NAnt directory in order to build a project or does it do it by "other means"?

感谢。

推荐答案

CC.NET有一些现有的XSL插件菜单系统。

CC.NET has a few existing "Xsl Plugins" in the menu system.

让我们的NUnit为例。

Let's take NUnit for example.

好吧，如果你从你的项​​目的构建的网页CC.NET点击NUnit的结果，你不会看到任何东西（开箱即用）。

Well, if you click the NUnit Results from the CC.NET webpage on your project's build, you won't see anything (out of the box).

为什么呢？
因为在保存所有有关生成的信息的超级骗子xml文件没有NUnit的XML数据。

Why? Because there is no NUnit xml data in the "super-duper" xml file that holds all the info about the build.

那么，如何实现这个目标？

So how does it get there?

一种方法是运行NUnit的命令行，它会创建一个输出XML文件。

One way is to run the NUNit command line, and it will create an output xml file.

NUnit.2.5.3.exe (bunch of stuff) NUnitResults.xml

（以上不工作code，只是在这一点上的概念推出，请）

(the above isn't working code, just roll with the concept at this point, please)

所以上面的命令行将创建文件NUnitResults.xml。
但是，即使你这样做，这个信息是不是在超级骗子的XML文件。

So the above command line will create a file NUnitResults.xml. But even if you do that, this info isn't in the "super-duper" xml file.

CC.NET有一个文件/合并的任务，这将需要一个独立的XML文件，而它吸进的超级骗子的XML文件。

CC.NET has a "File/Merge" task, that will take a standalone xml file, and "suck it into" the super-duper xml file.

在这个文件合并发生，现在NUnit的数据将是超级骗子的XML文件，而现在当你点击CC.NET项目NUnit的链接/建造页面中，会有NUnit的XML的在超级duper.xml文件数据，而XSL转换实际上会做一些事情，并创建你的cc.net项目的一些HTML输出/建造页面。

After this file-merge takes place, NOW that Nunit data will be in the super-duper-xml file, and now when you click the NUnit link on the CC.NET project/build page, there will be NUnit xml-data in the super-duper.xml file, and the xsl transform will actually do something, and create some html output on your cc.net project/build page.

这是否有道理？

下面是需要一些独立的XML和它吸进超duper.xml文件cc.net任务：

Here is the "take some stand alone xml and suck it into the super-duper.xml file" cc.net task:

http://confluence.public.thoughtworks.org/display/ CCNET /文件+合并+任务

下面是NUnit的CC.NET任务。现在，你不必使用CC.NET任务。您也可以（我做的方式）是丝在我的构建脚本的EXEC任务，该任务创建NUnit.xml数据。
阿卡，还有对皮肤有猫的几种方法。但我通常远离专有cc.net任务离开时，有一种不同的方式。为什么？因为如果我摆脱cc.net（到TFS为例），我的过渡将是那么痛苦。

Here is the NUNit CC.NET task. Now, you don't have to use the CC.NET task. You can also (and the way I do it) is wire up an EXEC task in my build script and that task creates the NUnit.xml data. Aka, there are a few ways to skin a cat. But I typically stay away from the proprietary cc.net tasks when there is a different way. Why? Because if I ever move from cc.net (to tfs for example), my transition will be less painful.

的http://confluence.public.thoughtworks.org/display/CCNET/Using+CruiseControl.NET+with+NUnit

这篇关于如何巡航控制.NET应用构建/测试工具？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！