Inspections (ReSharper)

The Inspections (ReSharper) build runner allows you to use the benefits of the JetBrains ReSharper code quality analysis feature right in TeamCity, with the help of the bundled JetBrains ReSharper Command Line Tools. You can use the tools within TeamCity without any additional ReSharper license.
ReSharper analyzes your C#, VB.NET, XAML, XML, ASP.NET, ASP.NET MVC, JavaScript, HTML, CSS code, and allows you to:

Find probable bugs
Eliminate errors and code smells
Detect performance issues
Improve the code structure and maintainability
Ensure the code conforms to guidelines, standards and specifications

ReSharper command line tools 2018.2 or newer require .NET Framework 4.6.1 or newer.

If you want to run ReSharper inspections using a specific ReSharper version (for example, to ensure it matches the version you have installed in Visual Studio), you can install another version of the tools and change the default version to be used on the Administration | Tools page. This page contains reference information about the Inspections (.NET) build runner's fields.

You can also refer to the ReSharper documentation for more details.

Sources to Analyze

Option	Description
Solution file path	The path to the `.sln` file created by Microsoft Visual Studio 2005 or later. The specified path should be relative to the checkout directory.
Projects filter	Specify project name wildcards to analyze only a part of the solution. Leave blank to analyze the whole solution. Separate wildcards with new lines. Example: JetBrains.CommandLine.* .Common .Tests.*

Environment Requirements

Option	Description
Target Frameworks	This option allows you to handle the Visual Studio Multi-Targeting feature. Agent requirement will be created for every checked item. .NET Framework versions 2.0 – 4.7.2 are supported. .NET Frameworks client profiles are not supported as target frameworks.

Option

Description

Target Frameworks

This option allows you to handle the Visual Studio Multi-Targeting feature.
Agent requirement will be created for every checked item.

.NET Framework versions 2.0 – 4.7.2 are supported.

JetBrains ReSharper Command Line Tools Settings

Option	Description
R# CLT Home Directory	Select the ReSharper Command Line Tools version. You can check the installed JetBrains ReSharper Command Line Tools versions on the Administration \| Tools page. If you want to run ReSharper duplicates using a specific ReSharper version (for example, to ensure it matches the version you have installed in Visual Studio), you can use this page to install another version of the tools and change the default version to be used.
InspectCode Platform	Select the platform bitness of the InspectCode tool. To find code issues in C++ projects, use the x86 platform.

Option

Description

R# CLT Home Directory

Select the ReSharper Command Line Tools version. You can check the installed JetBrains ReSharper Command Line Tools versions on the Administration | Tools page. If you want to run ReSharper duplicates using a specific ReSharper version (for example, to ensure it matches the version you have installed in Visual Studio), you can use this page to install another version of the tools and change the default version to be used.

InspectCode Platform

Select the platform bitness of the InspectCode tool. To find code issues in C++ projects, use the x86 platform.

InspectCode Options

Option	Description
Custom settings profile path	The path to the file containing ReSharper settings created with JetBrains Resharper 6.1 or later. The specified path should be relative to the checkout directory. If specified, this settings layer has the top priority, so it overrides ReSharper build-in settings. By default, build-in ReSharper settings layers are applied. For additional information about the ReSharper settings system, see ReSharper Web Help and JetBrains .NET Tools Blog
Enable debug output	Check this option to include debug messages in the build log and publish the file with additional logs (`dotnet-tools-inspectcode.log`) as a hidden artifact.
Additional inspectCode.exe arguments	Specify newline-separated command line parameters to add to calling `inspectCode.exe`. Only XML reports are supported by the runner. To get the output XML report, specify the path to the output file here via the `-o` or `–output` additional command line arguments. The paths relative to the build checkout directory as well as absolute paths are supported.

Option

Description

Custom settings profile path

The path to the file containing ReSharper settings created with JetBrains Resharper 6.1 or later.
The specified path should be relative to the checkout directory.
If specified, this settings layer has the top priority, so it overrides ReSharper build-in settings. By default, build-in ReSharper settings layers are applied.

For additional information about the ReSharper settings system, see ReSharper Web Help and JetBrains .NET Tools Blog

Enable debug output

Check this option to include debug messages in the build log and publish the file with additional logs (dotnet-tools-inspectcode.log) as a hidden artifact.

Additional inspectCode.exe arguments

Specify newline-separated command line parameters to add to calling inspectCode.exe.

Build Failure Conditions

If a build has too many inspection errors or warnings, you can configure it to fail by setting a build failure condition.

Build before analyze

In order to have adequate inspections execution results, you may need to build your solution before running analysis. This pre-step is especially actual when you use (implicitly or explicitly) code generation in your project.

Bundled ReSharper Versions

This section provides information on the versions of ReSharper bundled with TeamCity 2018+ versions.

TeamCity Version	ReSharper Version
2018.1	2018.1.2
2018.2	2018.1.4
2019.1	2019.1.1
2019.2	2019.2.3

You can view the installed versions of ReSharper on the Server Administration | Tools page. The bundled version is set as default; you can install other versions and change the default settings.