TeamCity Upgrade approach from 9.1.7 to 2018.1.3

Avatar
Permanently deleted user
Created

Hi JetBrains Team,

 

I am process of upgrading the TeamCity 9.1.7 to 2018.1.3 and following approach i have came up with

  1. Create backup of TeamCity server and its agents (we have total 4 agents and one is local agent which is installed along with TeamCity server ).
  2. Take backup of database as we are using the SQL Server as an external database.
  3. Note the username used to run the TeamCity server and its agents. This will be used during the new version installation.
  4. Run the new installer (2018.1.3) and point it to the same place TeamCity is installed into. Confirm uninstalling the previous installation.
  5. Proceed with 2018.1.3 installer which will install new files.
  6. Configure the TeamCity server windows service user accounts as we have used in 9.1.7 and do not select the agent feature during the installation dialog. Proceed with installation.
  7. After the installation, review the information displayed in WebUI which will upgrade the database (SQL Server in our case)
  8. After successful upgrade TeamCity should display new UI.

One issue i faced before upgrade was, i had the Agent which was installed on same server where we have TeamCity and in same directory, during the upgrade TeamCity wiped out the build agent directory which led the agent in situation where agent upgrade failed. The work around for this was to remove the agent windows service and move the agent directory to another location and install the agent service again. With this work around i was able to upgrade from 8.1.7 to 2018.1.3 on a test server.

Please let me the above steps will suffice the upgrade and i can move ahead and perform upgrade on actual production instance.

Please help

 

Thanks,

Chetan

 

 

Votes

0

Share

1 comment
Avatar
Denis Lapuente
Created

Hi Chetan,

 

those steps seem fine, pretty much the steps described in our upgrade instructions: https://confluence.jetbrains.com/display/TCD18/Upgrade

 

Build agents usually require no backups, nor a new installation. They should be upgraded on their own once they connect to the upgraded server. If they hold big repositories and their states require holding their work folder, that will be kept. If you have the default installation with the build agent within it, it would be wiped and reinstated, but it shouldn't fail to upgrade afterwards. The issue is very likely separate and should be investigated separately.

0

Please sign in to leave a comment.