Ccnet + msbuild + SVN daily build (2) automatically publish and deploy files after compilation

<Cruisecontrol>

<Project>
<Weburl> http: // 127.0.0.1/ccnet/viewfarmreport. aspx </weburl>
<Name> test4 </Name>
<Sourcecontrol type = "SVN" autogetsource = "true">
<Trunkurl> https://luyifeng.corp.ganji.com: 8443/SVN/helloword/test-SVN/mvcapplication1/trunk/</trunkurl>
<Executable> D: \ Program Files (x86) \ visualsvn Server \ bin \ svn.exe </executable>
<Workingdirectory> E: \ dailybuild \ mvctest1 </workingdirectory>
<Username> luyifeng </username>
<Password> luyifeng1 </password>

</Sourcecontrol>
<Tasks>

<Msbuild>
<Executable> C: \ WINDOWS \ Microsoft. NET \ framework \ v4.0.30319 \ msbuild.exe </executable>
<Workingdirectory> E: \ dailybuild \ mvctest1 </workingdirectory>
<Projectfile> mvcapplication1.sln </projectfile>
<Logger> D: \ Program Files (x86) \ cruisecontrol. Net \ Server \ thoughtworks. cruisecontrol. msbuild. dll </logger>
<Targets> build </targets>
<Timeout> 1900 </timeout>
<Buildargs> </buildargs>
</Msbuild>

<Msbuild>
<Executable> C: \ WINDOWS \ Microsoft. NET \ framework \ v4.0.30319 \ msbuild.exe </executable>
<Workingdirectory> D: \ soft \ ccnet \ test-SVN \ mvcapplication1 \ mvcapplication1 </workingdirectory>
<Projectfile> mvcapplication1.csproj </projectfile>
<Logger> D: \ Program Files (x86) \ cruisecontrol. Net \ Server \ thoughtworks. cruisecontrol. msbuild. dll </logger>
<Targets> _ wppcopywebapplication </targets>
<Timeout> 900 </timeout>
<Buildargs>/P: Platform = anycpu; configuration = debug; webprojectoutputdir = E: \ dailybuild \ mvc_test_publish/V: m </buildargs>
</Msbuild>

----- Add this configuration on the basis of ccnet + msbuild + SVN daily build (1). You can understand the general meaning by looking at the configuration.

---- Compile the WEB Project in the solution and use webprojectoutputdir = E: \ dailybuild \ mvc_test_publish
Publish to the specified directory,

--- For example, the IIS Directory of the test environment, so you do not need to manually deploy the test environment, it is very convenient to build the test environment

--- However, this may cause a problem. If the IIS directory is automatically released to the testing environment after each compilation is completed, the testing environment is often deployed and restarted, and the testing personnel cannot work normally.

--- The next article will solve this problem and explain how to disable automatic deployment to the IIS testing environment after compilation.

</Tasks>

<Publishers>
<Statistics/>
<Xmllogger/>
<Email from = "ganjialert@gmail.com" mailhost = "smtp.gmail.com"
Mailhostpassword = "ganji.com" mailhostusername = "ganjialert" usessl = "true"
Includedetails = "true">
<Users>
<User name = "luyifeng" address = "luyifeng@ganji.com" group = "developers"/>
</Users>
<Groups>
<Group name = "developers">
<Communications>
<Notificationtype> failed </notificationtype>
<Icationicationtype> exception </notificationtype>
</Communications>
</Group>
<Group name = "buildmaster">
<Communications>
<Icationicationtype> always </notificationtype>
</Communications>
</Group>
</Groups>
</Email>
<Modificationhistory onlylogwhenchangesfound = "true"/>
</Publishers>
<Triggers>
<! -- Buildcondition = "forcebuild" -->
<Intervaltrigger name = "continuous" seconds = "30"/>
</Triggers>
</Project>

</Cruisecontrol>