TeamCity Upgrade and HSQL migration

Avatar
N Basker
Created

Greetings:

Our setup is currently running TeamCity  2020.1.2 (build 78726) and uses HSQL internal database. The installation is on Ubuntu VM and the TeamCity server and build-agent are run as docker containers on the VM.

The plan is to do the following.

  1. Upgrade to TeamCity 2022.10.1 (build 116934)
  2. Migrate from HSQL to PostgreSQL external database after the upgrade

Checked the license and there is valid license until 28/09/2023.

Based on reading the documentation for TeamCity upgrade, would like to setup a Test-Drive as mentioned at How To... | TeamCity On-Premises Documentation (jetbrains.com)

A few clarifications here;

  1. As per the documentation, after setting up the test-server using a temporary license, migrating the data and if after doing all tests thinking of migrating HSQL to PostgreSQL (external). Then would like to transition this server as the main production one and decommission the current one running 2020.1.2 TeamCity. Is this possible, the documentation talks about running the test and coming back to upgrading the production server again. Would like to know if cut-over is possible.
  2. In the current production version, the TeamCity version 2020.1.2 is running on Ubuntu 16.05. As a part of test-server, would like to move to Ubuntu 22.05 and then run TeamCity 2020.1.2 and then restore the backup from production and try TeamCity upgrade. Would like to know if TeamCity 2020.1.2 can run on Ubuntu 22.05.

Thanks,

Nic

Votes

0

Share

5 comments
Avatar
Anatoly Cherenkov
Created
Hi! 1 - Yes, you can transition to the test server and decommission the original server:
https://www.jetbrains.com/help/teamcity/how-to.html#Move+TeamCity+Installation+to+a+New+Machine

2 - TeamCity is supported on all recent Ubuntu versions:
https://www.jetbrains.com/help/teamcity/supported-platforms-and-environments.html#Supported+Platforms+for+TeamCity+Server
0
Avatar
N Basker
Created

Thanks for the response, I have one follow up question.

Based on the documentation "Move TeamCity Installation to a NewMachine", we need to follow the "copying" approach which is documented here. Need to bring up the test-server with copied data and test. So, for a period of time, the expectation is to have both current-production and test-server of TeamCity running. In this context, since the same license cannot be used as per the documentation, can I take the following approach.

  1. Bring up the test-TeamCity 2022.10.1 on a new VM with temporary license.
  2. Copy the data from current-production to the test-TeamCity and test to make sure all that is needed is working.
  3. Migrate from HSQL to PostgreSQL and do all the testing. (Question, does the migration to PostgreSQL need full license, can this be done with temporary license)
  4. When ready to make the test-TeamCity new production, plan is to bringdown current-production TeamCity, copy the license from datadir/config/license.key to the test-TeamCity server and transition the test-TeamCity to New-Production service.
0
Avatar
Anatoly Cherenkov
Created
The outlined approach looks good.
As for the PostgreSQL question, you can use TeamCity with any supported database engine of your choice, regardless of the license you are using.
0
Avatar
N Basker
Created

Thanks again for the quick response. Just one more clarification.

Is there a recommendation to be in the same version 2020.1.2 (build 78726) of TeamCity server and first migrate HSQL to an external-database first and then upgrade to TeamCity 2022.10.1 (build 116934). Or upgrade TeamCity server version first and then migrate DB. Is there recommended best practice.

0
Avatar
Anatoly Cherenkov
Created
There should not be much difference if you do those steps in either order. I would suggest avoiding taking both steps at a time though (i.e., restoring the data into an external DB at the same time as you migrate the server). Because if any issues arise, it might be a little more effort required to tell the reason.
0

Please sign in to leave a comment.