如何用CruiseControl.Net来进行持续化集成(1)

最新推荐文章于 2025-08-15 08:51:41 发布

原创最新推荐文章于 2025-08-15 08:51:41 发布 · 635 阅读

0 ·

CC 4.0 BY-SA版权

.NET技术学习历程同时被 2 个专栏收录

42 篇文章

订阅专栏

架构

33 篇文章

订阅专栏

本文阐述了构建连续集成系统所需的关键组件，包括开发者PC、源代码控制系统、构建服务器、构建服务器可视化工具、问题/错误跟踪系统等。通过合理配置这些组件，可以实现项目的自动化构建、测试和部署。

The following services/roles are needed for a Continuous Integration System:

developer PC (duh)
source control server
build server
build server visualizer
issue/bug tracker

Build Server

This would be CCNet :-), installed on a server/machine of your choice. Depending on the amount of projects, the size, activity or the kind of actions you do,
one or more build servers can be needed.

Build Server Visualizer

This would be CCNet: CCTray and the webDashboard, both can visualize multiple CCNet build servers.
Another nice one is Cradiator This is a WPF-frontend that shows the state of CCNet projects on a big screen, making it ideal to give an overview for a team in the same room.

Issue/bug tracker

Even a piece of paper can do this trick, or an excel sheet, but a real issue tracking system is always neat. CCNet has some integration with issue-tracking systems see IssueUrlBuilder
SourceForge also offers issue tracking like Trac and DotProject.

http://www.cnblogs.com/jillzhang/archive/2008/03/03/1089099.html