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

最新推荐文章于 2019-08-02 09:10:17 发布

lein_wang

最新推荐文章于 2019-08-02 09:10:17 发布

阅读量461

点赞数

CC 4.0 BY-SA版权

分类专栏： .NET技术学习历程架构

本文链接：https://blog.youkuaiyun.com/lein_wang/article/details/8461790

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

42 篇文章

订阅专栏

架构

33 篇文章

订阅专栏

本文详细介绍了源代码的高效组织结构和版本控制的重要性，包括如何设置主干、分支，以及如何确保团队成员快速获取最新代码状态，避免版本混乱。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

Step 1 Setting up Source Control

Most systems I've seen have a setup as below :

ProjectName
  \__Trunk
  |    \Lib
  |    \Src
  \__Branches
       \__1_0_0_3450
       |  \Lib
       |  \Src
       \__1_0_1_5678
          \Lib
          \Src

Trunk is the 'line' where you'll do your every day work. This has 2 main folders : Lib and Src.
Lib holds any assembly's you use in the code : 3rd party assemblies.
Src holds the actual source.

These folders may off course have sub-folders.

Sometimes there are other folders also, like Tools (also directly under Trunk)

When you place a reference, it must be to the lib folder, or to standard .Net runtime which resides in the Global Assembly Cache.

The benefits of this setup :

when a new developer joins the team, he only needs to get the latest situation from source control, and he can start. No hours lost finding the correct version of a tool or library.
when you need to do a fix on an older version, you'll have the correct versions of all 3rd party assemblies and tools.

比较常用的组织源代码的层次结构。