根据我的需要选择正确的CI服务器 [英] Choosing the correct CI Server for my needs

问题描述

我正在为一个主要项目研究/设置一个持续集成服务器，并且需要提出建议或批评。

需要

CI只是我们路径中的下一步。它在正确的时间被授权，因为一个主要项目正在筹备中。

限制

• 需要与我们的SCM系统（SVN）位于同一个服务器上


• 服务器是（不幸的是）XP Pro机器。


• 需要处理.NET构建版本。


• 想要有一些分析功能。或者在以后添加的能力。


• 预算，免费优惠。


• 虽然我们的能力超强，但配置更容易。


• 我们的SVN网络前端正在使用apache。


• 使用NAnt建立

我将其缩小到目前为止

我目前正在查看4个选项：

• Cruise


• CruiseControl.NET


• TeamCity - 目前测试，

我的是什么？真实问题

在您使用任何或所有上述内容时，您所看到的任何批评或整洁的事情是什么。任何事情要注意，或在设置过程中注意？

解决方案

你看过/认为哈德森吗？ / p>

https://hudson.dev.java.net /

如果你正在用NAnt构建你的.NET项目，它有一个插件可以
允许它满足你的需求

它与大多数SCM系统，错误跟踪器等集成，并且极其可扩展。

根据我的经验，Hudson在大多数战线上都优于Cruise *。任何时候
我需要将它连接到别的，有人已经创建了一个插件。

它很容易配置，有大部分的电流插件软件工程
实践。它包括Winstone，可以完全独立运行，或者在任何
Java App / Servlet容器中。我已经有零个问题运行它在Tomcat和Glassfish
例如。

以下是其当前插件的列表

http://wiki.hudson-ci.org/display/ HUDSON / Plugins

似乎符合您的目标

  *需要能够与我们的SCM系统（SVN）位于同一服务器上
  

问题

  *服务器是（不幸的是）XP Pro机器。 
 

我没有在Win XP上运行独立版本的任何问题，
haven' t尝试它在XP上的其他服务器/容器上。

  *需要处理.NET构建。 
  

假设NAnt满足你的需要或者你已经在使用它， $ b短序

  *想拥有一些分析功能。或者在以后添加的能力。 
  

如果现有的插件不能满足您的需要，插件框架非常好，你
滚自己。

  *预算，免费优惠。 
  

免费且积极开发/维护

  *虽然我们的能力，配置将更容易。 
  

配置简单快捷。

  *我们的SVN Web前端使用apache。想要CI的前端做同样的事情，但可以处理IIS否则。 
  

这可能是一个问题，但如果包含的Winstone不能工作， / Servlet容器。

我已经将一些项目转换为使用CruiseControl的Hudson，并且没有回头。

尊敬

I am in the process of researching/setting up a Continuous Integration Server for a major project and am in the need of either recommendations or criticism.

The Need
CI is just the next step in our path. It's been mandated at the right time, as a major project is in the pipeline.

The Limitations

• Needs to be able to live on the same server as our SCM system (SVN)
• The Server is (unfortunately) an XP Pro Machine.
• Needs to handle .NET builds.
• Would like to have some profiling capability. Or the ability to add at a later date.
• Budget, free preferred.
• While we're more than capable, configuration would be preferred to be easy.
• Our SVN web front end is using apache. Would like the CI's front end to do the same, but can deal with IIS otherwise.
• Building with NAnt

What I've Narrowed it down to thus far
I am currently looking at 4 options:

• Cruise
• CruiseControl.NET
• TeamCity - Currently testing, seems to be good so far, the free pro edition has more than enough agents for our project.
• Hudson

What's my real question
In your experience with any or all of the above, what are any criticisms or neat things you have seen. Any things to watch out for, or pay attention to during setup? If you had to do it all over again, would you choose the same thing?

解决方案

Have you seen/considered Hudson ?

https://hudson.dev.java.net/

If you're building your .NET project with NAnt for example, it has a plugin that may allow it to serve your needs.

It integrates with most SCM systems, bug trackers, etc. and is extremely extensible.

In my experience, Hudson has been superior to Cruise* on most fronts. Anytime I've needed to connect it to something else, someone has already created a plugin.

It's easy to configure, has plugins for most aspects of current software engineering practices. It includes Winstone and can run completely standalone, or within any Java App/Servlet container. I've had zero issues running it in Tomcat and Glassfish for example.

Here's the list of its current plugins

http://wiki.hudson-ci.org/display/HUDSON/Plugins

It seems to meet your goals

* Needs to be able to live on the same server as our SCM system (SVN)

no problem

* The Server is (unfortunately) an XP Pro Machine.

I have not personally had any issues running the standalone variant on Win XP, haven't tried it on other servers/containers on XP though.

* Needs to handle .NET builds.

Assuming NAnt meets your needs or you're already using it, should be good to go here in short order

* Would like to have some profiling capability. Or the ability to add at a later date.

If existing plugins can't accommodate your needs, plugin framework is excellent and you could roll your own.

* Budget, free preferred.

Free and actively developed/maintained

* While we're more than capable, configuration would be preferred to be easy.

Config is quick and easy.

* Our SVN web front end is using apache. Would like the CI's front end to do the same, but can deal with IIS otherwise.

This may be a sticking point, but if the included Winstone won't work, it needs an App/Servlet container.

I've converted a few projects to Hudson which were using CruiseControl, and haven't looked back. I also push it for new projects whenever possible.

Regards

这篇关于根据我的需要选择正确的CI服务器的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！