I've done this successfully by:
1) Disabling the project on the original server (or shutting down
CC.NET until the files/folders below are copied)
2) Copying the project specific ".state" file (e.g.
"x.x.x_myproject.state") from the original CC.NET server folder to the
new server
3) Copying the project specific subfolder (e.g.
"x.x.x_myproject.state") from the original CC.NET server folder to the
new server
4) If the <xmllogger> or any other publisher elements refer to
specific locations, coping the folders they reference to the new
server with the exact same structure (or modify the elements as
necessary in the next step)
5) Creating a new project on the new server using the exact same
project name
I use pretty basic project configurations as shown below that uses
defaults for artifacts, workingdirectory and xmllogger (my Visual
Build Pro scripts do all the heavy lifting).
<project name="5.13.1-AutoRecService">
<category>5.13.1</category>
<webURL>http://$(servername)/ccnet/server/local/project/5.13.1-
AutoRecService/ViewLatestBuildReport.aspx</webURL>
<maxSourceControlRetries>10</maxSourceControlRetries>
<sourceControlErrorHandling>ReportOnRetryAmount</
sourceControlErrorHandling>
<triggers>
<intervalTrigger seconds="90" />
</triggers>
<sourcecontrol type="svn" autoGetSource = "false">
<trunkUrl>$(SVN_URL)/svn/Novar/branches/5.13.1/Solutions/Novar/
Standard Apps/AutoRecService</trunkUrl>
<executable>$(CC_FILES)\bin\svn.exe</executable>
<username>$(SVN_User)</username>
<password>$(SVN_Pass)</password>
</sourcecontrol>
<tasks>
<exec>
<executable>visbuildcmd.exe</executable>
<baseDirectory>C:\Program
Files\VisBuildPro6</baseDirectory>
<buildArgs>/b
"D:Source\5.13.1\BuildFiles\AutoRecService.bld"</
buildArgs>
<buildTimeoutSeconds>3600</buildTimeoutSeconds>
</exec>
</tasks>
<publishers>
<xmllogger />
</publishers>
</project>
Good luck,
Tom
On Nov 1, 7:38 am, "Philip Sayers" <[email protected]> wrote:
> If you have each build isolated to its own working directory... you should
> be able to just copy the whole directory tree for a given build over to the
> "Builds" folder on the new server. As long as your ccnet config file is
> pointing to the correct relative locations (in case you moved from a drive
> "D" to a drive "F" or something on the new box) it should "just work".
>
> Move them one at a time, and use the first one as a way to work out what
> paths you may need to tweak in your ccnet config or other build scripts.
> Use the list for the rest of them once the first build is working.
>
>
>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On
>
> Behalf Of Robert Duffy
> Sent: Monday, October 25, 2010 6:52 PM
> To: ccnet-user
> Subject: [ccnet-user] Moving CCnet projects to new servers
>
> I currently use CCnet to do my builds. We use it in combination with
> ClearCase and have had no real problems generating builds using
> MSBuild and ClearCase. We've come to a crossroad where we can not
> generate builds in parallel due to a problem we've run into using
> InstallShield to generate our MSI's. So, I'd like to move projects to
> new servers, and give them their own host for the builds. The problem
> is, I haven't been able to figure out how to get the "correct"
> arrtifacts on to the new servers to preserve the ClearCase label step
> we do. we have teamX_<bld label>. Some of our builds are into the
> 500 or 600 range. The only way around this I've found was to create a
> mocked up project and run it 600 times to get the artifact to the
> correct build #. If there's a way to do this, I haven't found it.
> And I thought I've copied across about every artifact I could find in
> the ccnet folder structures.
>
> Any help would be grand.
>
> Thanks
> Rob- Hide quoted text -
>
> - Show quoted text -
