Migrated TeamCity server seems not to pick up new licenses

We replaced an old TeamCity 2017 Server with 8 agents running on AWS with a new TeamCity server running version 2022.10.1 on GCP.

The new TeamCity server has been set up from scratch, the old build configurations have been first exported from the old server, and imported into a local TeamCity 2017 server installation. The TeamCity 2017 server install has been upgraded to 2022.10.1, and the build configurations have been exported and imported into the newly set-up server.

We have tested all the builds for a while using the 3 included agent licenses, and now we have bought an additional 17 licenses and have successfully added them. The cloud profile indeed starts 20 (3 included + 17 purchased) agents, but only 8 agents seem to be deployed on the 20 available instances.

It seems like the old number of 8 agents is still somewhere stored, so the 20 agents are not all being deployed, despite the GCP cloud profile having a limit of 20 instances and the server having 20 valid license keys entered.

Any idea where we would need to change settings to have the full 20 agent licenses being picked up?


Note that a server restart did not help either


Please take a look at Administration | Licenses on your new TeamCity server to see if there are any issues with your old license. Also, it might be necessary to contact our Sales Team to make sure your old licenses are compatible with TeamCity 2022.10.1. If the licenses are current, they can convert your old license to be compatible with the newer TeamCity release for you.

For additional information on TeamCity Upgrades and Licenses, please see https://www.jetbrains.com/help/teamcity/upgrading-teamcity-server-and-agents.html#Licensing.


The licenses have been bought just recently, for the new 2022.10.1 TeamCity server versions. You can see that by the fact that up to 20 GCP cloud agents are indeed started as VMs, but only 8 of those VMs seem to be running builds at the same time.

The 8 licenses we used for the previous 2017 TeamCity server have long expired already, which is why we have bought new licenses.


Sorry, I had misinterpreted your issue. So is TeamCity queuing any builds beyond 8 running builds, but it is starting agents even though the builds are queued? Or do you mean you're able to manually start up to 20 agents and TeamCity is queuing any builds beyond 8 running builds?

Also, is this occurring on a single build configuration or on the TeamCity server as a whole?


Looking at the Agents > Default > (our cloud image) > Agent Summary > Instances, there are actually 20 instances running and all of them seem to have an agent deployed (they use the same VM image in GCP, updating their agents on bootstrap of the image using a systemd service), but no builds beyond 8 concurrent builds are ever running.

We've tried this with all or our build configurations, it does not seem build configuration-specific. We've checked that all build configurations have set parallel builds to 0.

Do you have more insights which are possible settings we need to adjust?


If the builds beyond 8 are queued, it might be possible to check for a wait reason in the queue. Otherwise, we may be better off examining log files to look for some clues as to why only 8 builds are being run simultaneously.

Since you're a licensed user, you can open a support ticket by clicking the blue "Submit a Request" button at the top of this page. This way you can share log files with us confidentially. I'd suggest starting by looking at the teamcity-server.log and teamcity-cloud.log files.


Please sign in to leave a comment.