Setting up from scratch Part 01

简介: 原文:http://confluence.public.thoughtworks.org/display/CCNET/Setting+up+from+scratch++Part+01   Added by Ruben Willems , last edited by Rube...

原文:http://confluence.public.thoughtworks.org/display/CCNET/Setting+up+from+scratch++Part+01

 
Added by Ruben Willems , last edited by Ruben Willems on Sep 29, 2007  (view change)

We'll be setting it up step by step, so this will be a real step by step approach. The reason is you can see what the benefits are of the setups used in this document.
The first parts will seem overdone for users who used CCNet before, but it is intended for the real starters. Later parts contain tips/situations for people with the basic knowledge.

Typically a build system consists of 2 servers and X development machines, they can be on different physical machines, but they can also be hosted on 1 machine.
Or 1 physical machine with virtual machines on it, everything is possible

These 2 servers are :   
° Build server  : referenced as BuildServer
° Source Control server : referenced as SourceControl

For this example the setup will be on 1 machine, so everybody can follow this tutorial without having to maintain multiple PC's.

The easiest way to set things up is to respect the following installation order :
° windows
° IIS
° .Net framework
° Visual Studio
° extra tools (Nant, Testdriven.Net, NCover, ...)

Step 1 : Installing CCNet

Since it has an installer, it is in fact : setup, next, next, next, ...
Once this is done, you will have :
° a new folder in \Program Files : CruiseControl.Net
° a shortcut on the desktop : CruiseControl.Net
       This shortcut will start the build server.

Step 2 : Folder structure

Make the following folders

Folder Name Purpose
c:\Integration will contain the integration logs, artifacts, sources, ...
c:\Repository will contain the repository of our source control
c:\Projects will contain checked out sources to work with


note : this is not the best folder structure for sources, but for these example it will do fine.
          for setting up development trees, see Tree Surgeon (http://www.codeplex.com/treesurgeon),  CIFactory (http://www.cifactory.org/joomla), ...




 

Step 3 : First basic CCNet project

This project is just for playing around a bit with cruisecontrol, without having to do any real coding.
We'll just use a batch file, and play a bit with that.
Make a subfolder in c:\projects, named Example01
Create a command script named 'test.cmd' with the following contents

@echo off
set

 

If you run this script, you'll see all the environment variables of your machine.

Step 4 : Configuring the build server

Start the build service, (there is a desktop icon) you will see a command window wit the following :

[CCNet Server:DEBUG] The trace level is currently set to debug.  This will cause CCNet to log at the most verbose level,
which is useful for setting up or debugging the server.  Once your server is running smoothly, we recommend changing
this setting in C:\Program Files\CruiseControl.NET\server\ccnet.exe.config to a lower level.
[CCNet Server:INFO] Reading configuration file "C:\Program Files\CruiseControl.NET\server\ccnet.config"
[CCNet Server:INFO] No projects found
[CCNet Server:INFO] Registered channel: tcp
[CCNet Server:INFO] CruiseManager: Listening on url: tcp://192.168.131.72:21234/CruiseManager.rem
[CCNet Server:INFO] Starting CruiseControl.NET Server



Since there are no projects, we'll add one for this simple script. Leave the CCNet server running, it will pick up the changes to the config file after every save.
Modify CCNet.config, found in \program files\CruiseControl.Net\server
Enter the following text :
<cruisecontrol>
    <project>
        <name>SimpleExample</name>

	<triggers />

	<tasks>
	    <exec>
		<executable>c:\projects\test.cmd</executable>
	    </exec>
	</tasks>
    </project>
</cruisecontrol>

 

You'll see that the command window of the server added the following lines.

[680:INFO] Configuration changed: Restarting CruiseControl.NET Server
[680:INFO] Reading configuration file "C:\Program Files\CruiseControl.NET\server\ccnet.config"
[SimpleExample:INFO] Starting integrator for project: SimpleExample


 

Now you can also browse to the dashboard,

open your browser and surf to http://localhost/ccnet
you will see the project : SimpleExample

Press the 'Force' button to force the build. Next press 'Refresh Status' to view the result.

You see that the build was successfull

Clicking on the project name 'SimpleExample' will show a page with project related information. From there on you can go to individual builds.

This shows how to set up a very basic project in CCNet, the next topic will cover :

° improving the project setup
° setting up source control monitoring
° getting information about builds

相关文章
|
算法 网络协议 C语言
C/C++学习 -- HMAC算法
C/C++学习 -- HMAC算法
582 1
|
缓存 网络协议 算法
《跟闪电侠学Netty》阅读笔记 - Netty入门程序解析(二)
《跟闪电侠学Netty》阅读笔记 - Netty入门程序解析
358 1
|
存储 开发框架 Linux
DPDK学习之DPDK边界
DPDK学习之DPDK边界
515 0
|
Rust 测试技术 API
【Rust 实战】Rust与C#交互-生成DLL库
【Rust 实战】Rust与C#交互-生成DLL库
2474 0
【Rust 实战】Rust与C#交互-生成DLL库
|
Linux 数据处理
DPDK
数据平面开发套件(DPDK[1]  ,Data Plane Development Kit)是由6WIND,Intel等多家公司开发,主要基于Linux系统运行,用于快速数据包处理的函数库与驱动集合,可以极大提高数据处理性能和吞吐量,提高数据平面应用程序的工作效率。
2559 0
|
8天前
|
人工智能 JSON 供应链
畅用7个月无影 JVS Claw |手把手教你把JVS改造成「科研与产业地理情报可视化大师」
LucianaiB分享零成本畅用JVS Claw教程(学生认证享7个月使用权),并开源GeoMind项目——将JVS改造为科研与产业地理情报可视化AI助手,支持飞书文档解析、地理编码与腾讯地图可视化,助力产业关系图谱构建。
23428 9
畅用7个月无影 JVS Claw |手把手教你把JVS改造成「科研与产业地理情报可视化大师」
|
17天前
|
缓存 人工智能 自然语言处理
我对比了8个Claude API中转站,踩了不少坑,总结给你
本文是个人开发者耗时1周实测的8大Claude中转平台横向评测,聚焦Claude Code真实体验:以加权均价(¥/M token)、内部汇率、缓存支持、模型真实性及稳定性为核心指标。
6439 25
|
12天前
|
人工智能 缓存 BI
Claude Code + DeepSeek V4-Pro 真实评测:除了贵,没别的毛病
JeecgBoot AI专题研究 把 Claude Code 接入 DeepSeek V4Pro,跑完 Skills —— OA 审批、大屏、报表、部署 5 大实战场景后的真实体验 ![](https://oscimg.oschina.net/oscnet/up608d34aeb6bafc47f
4158 13
Claude Code + DeepSeek V4-Pro 真实评测:除了贵,没别的毛病