I recently had to migrate a Jetbrains TeamCity installation to a brand new server environment including a brand new instance of SQL Server.
If you have already read my earlier post: http://samirvaidya.blogspot.com/2015/02/migrating-teamcity-to-new-server-when.html, the process is pretty much the same as earlier.
One of the things that I noticed, however, after the migration was that my NuGet settings were not retained. Therefore, I had to update the version of my NuGet executable in the Administration section to point to the desired version.
That was all there was to it!!
If you have already read my earlier post: http://samirvaidya.blogspot.com/2015/02/migrating-teamcity-to-new-server-when.html, the process is pretty much the same as earlier.
- Install a fresh copy of Jetbrains TeamCity
- Stop the TeamCity Server and Build Agent services
- Copy over the TeamCityData directory to the new server (in some cases only the config and lib directories are needed)
- Restore the existing TeamCity database to the new SQL Server
- Update the database.properties file to point to the new SQL Server
- Restart the TeamCity Server and Build Agent services
- Verify that you can log into the new system
One of the things that I noticed, however, after the migration was that my NuGet settings were not retained. Therefore, I had to update the version of my NuGet executable in the Administration section to point to the desired version.
That was all there was to it!!
No comments:
Post a Comment