The Inspections (ReSharper) runner allows you to use the benefits of JetBrains ReSharper code quality analysis feature right in TeamCity using the bundled JetBrains ReSharper Command Line Tools. The usage of the tools within TeamCity does not require any additional licensing for ReSharper.
- 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
If you want to run ReSharper inspections using a specific ReSharper version (e.g. 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 using the Administration | Tools page.
This page contains reference information about the Inspections (.Net) Build Runner fields:
You can also refer to ReSharper documentation for more details.
Sources to Analyze
Solution file path
The path to .sln file created by Microsoft Visual Studio 2005 or later.
Specify project name wildcards to analyze only a part of the solution. Leave blank to analyze the whole solution.
This option allows you to handle the Visual Studio Multi-Targeting feature.
.Net Framework versions 2.0 - 4.7.2 are supported.
JetBrains ReSharper Command Line Tools Settings
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 (e.g. 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 can 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.|
Custom settings profile path
The path to the file containing ReSharper settings created with JetBrains Resharper 6.1 or later.
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.