自动化每日构建(三)用NAnt来完成.NET工程的每日构建
2004-07-21 17:13
441 查看
过去写的文章,不过是英文的。后面有附带的 project.build 文件,你可以用项目的名称替换调******,并且加上代码更新,单元测试等具体内容,就可以做每日构建了。
Start a new .NET project by using Nant This document has 5 sections: Brief System requirement Directories and files The Build file Run Nant
Every directory is made for a certain kind of files. Directory names and what kind of files should be put in list below:
Now Nant runs. We can EDIT the build file to add new features: unit testing, packing, deploying, etc, as you like.
project.build 文件内容:
<?xml version="1.0" ?>
<project default="usage" basedir=".">
<echo message="Using '${nant.settings.currentframework}' framework on '${nant.platform.name}' platform."/>
<!-- =================================================================== -->
<!-- Initialization target -->
<!-- =================================================================== -->
<target name="init">
<!-- You have to fill the ***** space with your project label. -->
<property name="Name" value="*****"/>
<property name="name" value="*****"/>
<property name="version" value="1.0" overwrite="false" />
<echo message="------------------ ${Name}${version} Build ------------------"/>
<property name="s.home" value=".."/>
<property name="s.src" value="${s.home}/src"/>
<property name="s.srccs" value="${s.home}/src/cs"/>
<property name="s.gohome" value="../"/>
<property name="s.lib" value="${s.home}/lib"/>
<property name="s.res" value="${s.home}/res"/>
<property name="s.build" value="${s.home}/build"/>
<property name="s.run" value="${s.home}/run"/>
<property name="s.build.assemble" value="${s.build}/assemble"/>
<property name="s.build.bin" value="${s.build.assemble}/bin"/>
<property name="s.build.debug" value="${s.build.bin}/debug"/>
<property name="s.build.gensrc" value="${s.build.assemble}/gen-src"/>
<property name="s.build.apidocs" value="${s.build}/apidocs"/>
<property name="s.build.lib" value="${s.home}/res"/>
<property name="s.build.release" value="${s.build}/release"/>
<property name="s.build.web" value="${s.build}/web"/>
<property name="s.build.dist" value="${s.build}/dist"/>
<property name="s.main" value="com"/>
<tstamp>
<format property="TODAY" pattern="d-MM-yy"/>
</tstamp>
</target>
<!-- =================================================================== -->
<!-- Help on usage -->
<!-- =================================================================== -->
<target name="usage">
<echo message=""/>
<echo message=""/>
<echo message="***** Build file"/>
<echo message="-------------------------------------------------------------"/>
<echo message=""/>
<echo message=" available targets are:"/>
<echo message=""/>
<echo message=" package --> generates the *****.zip file (default)"/>
<echo message=" compile --> compiles the source code"/>
<echo message=" test --> unit test"/>
<echo message=" release --> build the installation package"/>
<echo message=" deploy --> deploy the application"/>
<echo message=" clean --> cleans up the directory"/>
<echo message=""/>
<echo message=" See the comments inside the *.build file for more details."/>
<echo message="-------------------------------------------------------------"/>
<echo message=""/>
<echo message=""/>
</target>
<!-- =================================================================== -->
<!-- Compiles the source directory -->
<!-- =================================================================== -->
<target name="compile" depends="init">
<mkdir dir="${s.build.bin}"/>
<echo message=""/>
<echo message="Compiling application main source..."/>
<echo message="${s.srccs}/${name}/*.cs"/>
<!-- You may change the compile tasks here. -->
<!-- first compile way: using solution task -->
<solution configuration="release" solutionfile="${s.srccs}/${name}/${name}.sln"
outputdir="${s.build.bin}" />
<!-- second compile way: using csc task for c# file -->
<!--
<csc target="exe" warnaserror="true" debug="${debug}"
output="${s.build.bin}/${name}.exe" >
<sources failonempty="true">
<includes name="${s.srccs}/${name}/*.cs" />
</sources>
</csc>
-->
</target>
<!-- =================================================================== -->
<!-- Creates the zip package -->
<!-- =================================================================== -->
<target name="package" depends="compile">
<!-- You may change the package tasks here. -->
</target>
<!-- =================================================================== -->
<!-- Creates the deploy -->
<!-- =================================================================== -->
<target name="test" depends="compile">
<!-- You may fill the tasks here. -->
</target>
<!-- =================================================================== -->
<!-- Creates the deploy -->
<!-- =================================================================== -->
<target name="deploy" depends="">
<!-- You may fill the tasks here. -->
</target>
<!-- =================================================================== -->
<!-- Build the installation packge -->
<!-- =================================================================== -->
<target name="release" depends="clean">
<!-- You may fill the tasks here. -->
</target>
<!-- =================================================================== -->
<!-- Clean targets -->
<!-- =================================================================== -->
<target name="clean" depends="init">
<delete dir="${s.build.assemble}"/>
<delete dir="${s.build.release}"/>
<!-- You may fill the tasks here. -->
</target>
</project>
<!-- End of file -->
Start a new .NET project by using Nant This document has 5 sections: Brief System requirement Directories and files The Build file Run Nant
Brief
Start a new .NET project by using Nant, so we can make Daily Building. All have to do list below: 1.Install .NET SDK1.0 and new version Nant, and make Nant works. 2.Copy Directories and files from nproject(n for .NET) template library. 3.Make project files stay in the right directory. 4.Edit the project.Build file. Let it fit the project. 5.Run Nant.System requirement
.NET SDK1.0 or higher Nant 0.84 or higherDirectories and files
You can make directories yourself, or copy from template. But make sure the directory tree like this:Every directory is made for a certain kind of files. Directory names and what kind of files should be put in list below:
Directory Files should be put in
Build building files Data project’s data files Doc project‘s documents for installation and deploying Lib libraries project depending on Res resources project using Install resources for installation Src project’ source files Config project’s configuration files Database project’s database files cs project’s c# source code files Docs project’s documents for manager, developer, tester Scripts project’s script files Sql project’s script files for database Now put the .NET files into the /src/cs directory.The Build file
The build file is /build/project.build. In the template we already have a default build file. Because every project has different name and configuration, so we must edit the build file to suit project. We must edit the project name and path in the build file.Run Nant
After doing that, now start a command-line prompt, change path to ./build, and type nant. We can see a function list like this:Now Nant runs. We can EDIT the build file to add new features: unit testing, packing, deploying, etc, as you like.
project.build 文件内容:
<?xml version="1.0" ?>
<project default="usage" basedir=".">
<echo message="Using '${nant.settings.currentframework}' framework on '${nant.platform.name}' platform."/>
<!-- =================================================================== -->
<!-- Initialization target -->
<!-- =================================================================== -->
<target name="init">
<!-- You have to fill the ***** space with your project label. -->
<property name="Name" value="*****"/>
<property name="name" value="*****"/>
<property name="version" value="1.0" overwrite="false" />
<echo message="------------------ ${Name}${version} Build ------------------"/>
<property name="s.home" value=".."/>
<property name="s.src" value="${s.home}/src"/>
<property name="s.srccs" value="${s.home}/src/cs"/>
<property name="s.gohome" value="../"/>
<property name="s.lib" value="${s.home}/lib"/>
<property name="s.res" value="${s.home}/res"/>
<property name="s.build" value="${s.home}/build"/>
<property name="s.run" value="${s.home}/run"/>
<property name="s.build.assemble" value="${s.build}/assemble"/>
<property name="s.build.bin" value="${s.build.assemble}/bin"/>
<property name="s.build.debug" value="${s.build.bin}/debug"/>
<property name="s.build.gensrc" value="${s.build.assemble}/gen-src"/>
<property name="s.build.apidocs" value="${s.build}/apidocs"/>
<property name="s.build.lib" value="${s.home}/res"/>
<property name="s.build.release" value="${s.build}/release"/>
<property name="s.build.web" value="${s.build}/web"/>
<property name="s.build.dist" value="${s.build}/dist"/>
<property name="s.main" value="com"/>
<tstamp>
<format property="TODAY" pattern="d-MM-yy"/>
</tstamp>
</target>
<!-- =================================================================== -->
<!-- Help on usage -->
<!-- =================================================================== -->
<target name="usage">
<echo message=""/>
<echo message=""/>
<echo message="***** Build file"/>
<echo message="-------------------------------------------------------------"/>
<echo message=""/>
<echo message=" available targets are:"/>
<echo message=""/>
<echo message=" package --> generates the *****.zip file (default)"/>
<echo message=" compile --> compiles the source code"/>
<echo message=" test --> unit test"/>
<echo message=" release --> build the installation package"/>
<echo message=" deploy --> deploy the application"/>
<echo message=" clean --> cleans up the directory"/>
<echo message=""/>
<echo message=" See the comments inside the *.build file for more details."/>
<echo message="-------------------------------------------------------------"/>
<echo message=""/>
<echo message=""/>
</target>
<!-- =================================================================== -->
<!-- Compiles the source directory -->
<!-- =================================================================== -->
<target name="compile" depends="init">
<mkdir dir="${s.build.bin}"/>
<echo message=""/>
<echo message="Compiling application main source..."/>
<echo message="${s.srccs}/${name}/*.cs"/>
<!-- You may change the compile tasks here. -->
<!-- first compile way: using solution task -->
<solution configuration="release" solutionfile="${s.srccs}/${name}/${name}.sln"
outputdir="${s.build.bin}" />
<!-- second compile way: using csc task for c# file -->
<!--
<csc target="exe" warnaserror="true" debug="${debug}"
output="${s.build.bin}/${name}.exe" >
<sources failonempty="true">
<includes name="${s.srccs}/${name}/*.cs" />
</sources>
</csc>
-->
</target>
<!-- =================================================================== -->
<!-- Creates the zip package -->
<!-- =================================================================== -->
<target name="package" depends="compile">
<!-- You may change the package tasks here. -->
</target>
<!-- =================================================================== -->
<!-- Creates the deploy -->
<!-- =================================================================== -->
<target name="test" depends="compile">
<!-- You may fill the tasks here. -->
</target>
<!-- =================================================================== -->
<!-- Creates the deploy -->
<!-- =================================================================== -->
<target name="deploy" depends="">
<!-- You may fill the tasks here. -->
</target>
<!-- =================================================================== -->
<!-- Build the installation packge -->
<!-- =================================================================== -->
<target name="release" depends="clean">
<!-- You may fill the tasks here. -->
</target>
<!-- =================================================================== -->
<!-- Clean targets -->
<!-- =================================================================== -->
<target name="clean" depends="init">
<delete dir="${s.build.assemble}"/>
<delete dir="${s.build.release}"/>
<!-- You may fill the tasks here. -->
</target>
</project>
<!-- End of file -->
相关文章推荐
- 自动化每日构建(三)用NAnt来完成.NET工程的每日构建
- 自动化每日构建(二)用Ant来完成java工程的每日构建
- 自动化每日构建(二)用Ant来完成java工程的每日构建
- 自动化每日构建(一)用Ant来完成Delphi工程的每日构建
- 使用Flashbuilder/Flashbuilder-plugins搭建Flex工程每日构建(自动化构建)的方法
- 图解持续集成--纯命令行实现.Net项目每日构建(流程支持)
- 图解持续集成--纯命令行实现.Net项目每日构建(升级版本)
- Albacore--.NET下基于Rake(ruby make)的自动化构建工具
- 在.NET环境中实现每日构建--NAnt篇(转载)
- 在.NET环境中实现每日构建--NAnt篇
- Jenkins部署.net自动化构建
- 在.NET环境中实现每日构建(Daily Build)--NAnt篇
- 在CentOS上构建.net自动化编译环境
- Albacore--.NET下基于Rake(ruby make)的自动化构建工具
- 在.NET环境中实现每日构建(Daily Build)--ccnet,MSBuild篇
- 为了后面自动化部署,需要整理公司项目的maven依赖关系,eclipse下maven组件的安装以及用eclipse构建maven多模块工程(即有父子依赖关系的工程)遇到一个class not fond
- 主题:在ant中使用cvs功能自动完成每日构建
- 协作开发中的质量保证技术——并行版本控制、每日构建和交付工程
- 使用MAVEN进行工程自动化构建(1)
- 图解持续集成--纯命令行实现.Net项目每日构建(升级版本)