配置管理规范

$ cvs -q diff --brief -D "上一次编译日期"

NBDSCRIPT=/home/Administrator/work/jiangxin/src/nightlybuild/script/  
NBDSOURCE=/home/Administrator/work/jiangxin/src/dlltest/ 

#!/bin/sh
#set -x

NBDHOMEDIR=`dirname $0`

if echo "$NBDHOMEDIR" | grep -q -v  "^/"; then
	NBDHOMEDIR="`pwd`/${NBDHOMEDIR}"
fi

NBDHOMEDIR=${NBDHOMEDIR%\.}
NBDHOMEDIR=${NBDHOMEDIR%/}
export NBDHOMEDIR

build_file_name="${NBDHOMEDIR}/build.ini"

if [ ! -f "$build_file_name" ]; then
	echo "not find $build_file_name!" && exit 1
fi

. $build_file_name

cd $NBDSCRIPT
sh nightlybuild.sh "$@"

[myapp] 
module=RegDllTest otherapp 
version=1.3.5.10 
buildtime=2003-04-01 20:44:48 
revisonfile=RegDllTest/RegDllTest.rc 

[mydll]
module=DisplayAppName
version=2.1.3.19
buildtime=2003-02-12 10:21:08
revisonfile=DisplayAppName/DisplayAppName.rc

[global] 
version=1.0.0.1 
buildtime=2003-04-01 20:44:48

JOHNSON-V-1-0-1

Synopsis: nightly.sh [options...] [command...]
    Options :
        -release (-r) 
            build RELEASE version (default)
        -engineer (-e) 
            build engineer version
        -force (-f)  
            force build.

    Command:
        nightly (n)
            All commands are bind to one. there are three steps to run nightly.
            update, compile, link, post
        update (up) 
            1st step of running nightly.
            update_source_code         : step 1.1
            update_version_file        : step 1.2
            update_rc_file             : step 1.3
        compile (c) 
            2nd step of running nightly.
            run custom make.bat        : step 2.1
        link (l) 
            3rd step of running nightly.
            run custom link.bat        : step 3.1
        post (l) 
            4th step of running nightly.
            cp package to ftp_dir      : step 4.1
            checkin version file       : step 4.2
    Other Command:
        help  
            This screen.
        config
            Additional help.

        run nightly.sh config to see additional help. 

在实践中，会发现编译机和版本控制服务器的时钟同步非常重要。因为编译机确定编译的时间，是从本地取时钟，编译成功后，要将编译时间 checkin 到版本控制服务器，以便下次执行自动编译时，从该文件获取上次编译时间，比较两个时间间隔内有否代码改动。如果发布机的时钟和版本控制系统的时钟不一致，会导致代码更新的误判。

最近在网上发现了一篇文章，《A Beginner's Guide to Network Time Protocol--Other Time Software》，非常巧合的是，我在选择时间同步方案的时候，走了几乎相同的路。

对于工作组内平台相对单一，时钟同步是一件非常简单的事情：

加入 Windows 域的 Windows 平台的机器会定期和域控制服务器时钟同步。亦可以使用命令"net time /setsntp" 和 ntp 服务器时钟同步。

对于Unix服务器来说，则有更多选择的余地。例如：从最简单的使用13端口的 RFC867 daytime 协议；使用基于 RFC868 Time Protocol 的 rdate 命令从服务器读取时间来设置本地时间；运行 timed，保持 unix 机器自动同步时钟；以及用 ntp 协议和国际标准时同步。

对于复杂的网络环境，使用 ntp 确是上选。

Servers that provide synchronization to a sizeable population of clients normally operate as a group of three or more mutually redundant servers, each operating with three or more stratum-one or stratum-two servers in client-server modes, as well as all other members of the group in symmetric modes. This provides protection against malfunctions in which one or more servers fail to operate or provide incorrect time. The NTP algorithms have been specifically engineered to resist attacks where some fraction of the configured synchronization sources accidently or purposely provide incorrect time. In these cases a special voting procedure is used to identify spurious sources and discard their data.

参见：《A Beginner's Guide to Network Time Protocol (NTP)》, 《Notes on setting up a NTP subnet》...

Unix上的 NTP软件：

下载...

Windows上的 NTP客户端的配置：