Teamcity no longer comptible with Resharper CLT?
I'm unable to update the tool in our TeamCity Enterprise 2025.11.3 Build 208117.
Our server is airgapped, so we have to upload tools, we can't connect to jebrains or nuget to get the latest package. In the past we can just upload the nuget package for Resharper CLT or the ZIP from the jetbains website.
This no longer works with Resharper 2026.1, it complains about invalid package when I try and upload either of the 2026.1 Resharper packages.
I also noticed the Nuget package is no deprecated and replaced with a globaltools
NuGet Gallery | JetBrains.ReSharper.CommandLineTools 2025.2.5
NuGet Gallery | JetBrains.ReSharper.GlobalTools 2026.1.0
Anyone seen this, or know a workaround?
Thanks,
Please sign in to leave a comment.
Hi Mark,
Yes, this is a known issue. We have it tracked internally as TW-97464.
What is happening here is that starting with ReSharper 2026.1, the command line tools are distributed as a .NET tool instead of the old package format that TeamCity’s built-in Inspections (ReSharper) runner expects. Because of that, uploading the 2026.1 package directly in TeamCity can fail with “invalid package”, especially in air-gapped environments.
At the moment, the recommended workaround is to stop using the built-in Inspections (ReSharper) runner for this case, and instead run the inspection in 3 command line steps:
1. Install the tool
2. Run inspectcode
3. Import the report into TeamCity
For more details, please refer to the link.
Since your server is air-gapped, you would need to prepare the .NET tool package in a way that works for your offline environment, then install/run it via the .NET CLI on the build agent.
Unfortunately, the fix for this issue has been postponed for now due to other priorities and ongoing integrations changes, so this workaround is the current recommended approach.