Skip to end of metadata
Go to start of metadata

The Inspections (IntelliJ IDEA) Build Runner is intended to run code analysis based on IntelliJ IDEA inspections for your project. Since TeamCity 2017.1, in addition to the bundled version, it is possible to install another version of JetBrains IntelliJ Inspections and Duplicates Engine and/or change the defaults using the Administration | Tools page.

IntelliJ IDEA's code analysis engine is capable of inspecting your Java, JavaScript, HTML, XML and other code and allows you to:

  • Find probable bugs
  • Locate "dead" code
  • Detect performance issues
  • Improve the code structure and maintainability
  • Ensure the code conforms to guidelines, standards and specifications

Refer to IntelliJ IDEA documentation for more details.


To run inspections for your project, you must have either an IntelliJ IDEA project file (.ipr) or a project directory (.idea) checked into your version control.
The runner also supports Maven2 or above: to use pom.xml, you need to open it in IntelliJ IDEA and configure inspection profiles as described in the IntelliJ IDEA documentation. IntelliJ IDEA will save your inspection profiles in the corresponding folder. Make sure you have it checked into your version control. Then specify the paths to the inspection profiles while configuring this runner.

This page contains reference information about the following Inspections (IntelliJ IDEA) Build Runner fields:

IntelliJ IDEA Project Settings



Project file type

To be able to run IntelliJ IDEA inspections on your code, TeamCity requires either an IntelliJ IDEA project file\directory, Maven pom.xml or Gradle build.gradle to be specified here.

Path to the project

Depending on the type of project selected in the Project file type, specify here:

  • For IntelliJ IDEA project: the path to the project file (.ipr) or the path to the project directory the root directory of the project containing the .idea folder).
  • For Maven project: the path to the pom.xml file. 
  • For Gradle project: the path to the .gradle file.
    This information is required by this build runner to understand the structure of the project.


    The specified path should be relative to the checkout directory.

Detect global libraries and module-based JDK in the *.iml files

This option is available if you use an IntelliJ IDEA project to run the inspections. In IntelliJ IDEA, the module settings are stored in *.iml files, thus, if this option is checked, all the module files will be automatically scanned for references to the global libraries and module JDKs when saved. This helps ensure that all references will be properly resolved.



When this option is selected, the process of opening and saving the build runner settings may become time-consuming, because it involves loading and parsing all project module files.

Check/Reparse Project

This option is available if you use an IntelliJ IDEA project to run the inspections. Click this button to reparse your IntelliJ IDEA project and import the build settings right from the project, for example the list of JDKs.


If you update your project settings in IntelliJ IDEA (e.g add new jdks, libraries), remember to update the build runner settings by clicking Check/Reparse Project.

Working directory

Enter a path to a Build Working Directory if it differs from the Build Checkout Directory.Optional, specify if differs from the checkout directory.

Unresolved Project Modules and Path Variables

This section is displayed when an IntelliJ IDEA module file (.iml) referenced from an IntelliJ IDEA project file:

  • cannot be found
  • allows you to enter the values of path variables used in the IPR-file.

To refresh the values in this section, click Check/Reparse Project.




This field appears if the project file contains path macros, defined in the Path Variables dialog of IntelliJ IDEA's Settings dialog. In Set value to field, specify a path to the project resources to be used on different build agents.

Project SDKs

This section provides the list of SDKs detected in the project.



JDK Home

Use this field to specify the JDK home for the project.


When building with the Ipr runner, this JDK will be used to compile the sources of corresponding IDEA modules. For Inspections and Duplicate Finder builds, this JDK will be used internally to resolve the Java API used in your project.
To run the build process, the JDK specified in the JAVA_HOME environment variable will be used.

JDK Jar File Patterns

Click this link to open a text area where you can define templates for the jar files of the project JDK. Use Ant rules to define the jar file patterns.
The default value is used for Linux and Windows operating systems:

For Mac OS X, use the following lines:


If your project uses the IDEA JDK, specify the location of the IDEA home directory

IDEA Jar Files Patterns

Click this link to open a text area, where you can define templates for the jar files of the IDEA JDK.


You can use references to external properties when defining the values, like %system.idea_home% or %env.JDK_1_3%. This will add a requirement for the corresponding property.

Java Parameters




Select a JDK. This section details the available options. The default is JAVA_HOME environment variable or the agent's own Java.

JDK home path

The option is available when <Custom> is selected above. Use this field to specify the path to your custom JDK used to run the build. If the field is left blank, the path to JDK Home is read either from the JAVA_HOME environment variable on agent the computer, or from the env.JAVA_HOME property specified in the build agent configuration file ( If these values are not specified, TeamCity uses the Java home of the build agent process itself.

JVM command line parameters

You can specify such JVM command line parameters, e.g. maximum heap size or parameters enabling remote debugging. These values are passed by the JVM used to run your build.

Inspection Parameters

In IntelliJ IDEA-based IDEs, the code inspections reported are configured by an inspection profile.
When running the inspections in TeamCity, you can specify the inspection profile to use: first you need to configure the inspection profile in IntelliJ IDEA-based IDE and then specify it in TeamCity.

Follow these rules when preparing inspection profiles:

  • if your inspection profile uses scopes, make sure the scopes are shared;
  • lock the profile (this ensures that inspections present in TeamCity but not enabled in your IDEA installation will not be run by TeamCity);
  • ensure the profile does not have inspections provided by plugins not included into the default IntelliJ IDEA Ultimate distribution (otherwise they will just be ignored by TeamCity);
  • for best results, edit the inspection profile in the IntelliJ IDEA of the same version as used by TeamCity (can be looked up in the inspection build log).

The logic of selecting an inspection profile is as follows:

  • if the path to the inspection profile is specified, then the profile will be loaded from the file. If the loading fails, the inspection runner will fail too.
  • if the name of the inspection profile is specified, the profile is searched for in the project's shared profiles. If there is no such profile, the inspection runner will fail.
  • if neither the name nor path is specified, the default profile of the project is used.



Inspections profile path

Use this text field to specify the path to inspections profiles file relative to the project root directory. Use this field only if you do not want to use the shared project profile specified in "Inspections profile name".

Inspections profile name

Enter the name of the desired shared project profile. If the field is left blank and no profile path is specified, the default project profile will be used.

Include / exclude patterns:

Optional, specify to restrict the sources scope to run Inspections on.


Include / exclude patterns are newline-delimited set of rules of the form:

where the pattern must satisfy the following rules:

  • must end with either ** or * (this effectively limits the patterns to only the directories level, they do not support file-level patterns);
  • references to modules can be included as [<IDEA_module_name>]/<path_within_module>. If you have a Maven project configured, you can use Maven module's artifactId as <IDEA_module_name>;
  • the configured paths are treated as relative paths within content roots of the IDEA project modules. That is, the paths should be relative to the module's roots.

Some notes on patterns processing:

  • excludes have precedence over includes
  • if include patterns are specified, only directories matching these patterns will be included, all other directories will be excluded
  • the include pattern has a special behavior (due to underlying limitations): it includes the directory specified and all the files residing directly in the directories above the one specified.



For the file paths to be reported correctly, the "References to resources outside project/module file directory" option for the project and all modules should be set to "Relative" in IDEA project.

For Maven inspections run, to ensure correct Java is used for the project JDK, define env.JAVA_HOME configuration parameter pointing to the JDK to be used as the project JDK.

Getting the same results in IntelliJ IDEA and TeamCity Inspections Build

The code inspections reported by IntelliJ IDEA and TeamCity Java Code Inspections build depend on a number of factors. You would need to ensure equal settings in IntelliJ IDEA and the build to get the same reports.
The relevant settings include:

  • inspections profile used in IntelliJ IDEA and TeamCity build;
  • environment-specific project dependencies (files not in version control, etc.);
  • IDE-level settings, like defined SDKs, path variables, etc.;
  • generated files: should be present in the TeamCity agent if they are present when working with the project in IntelliJ IDEA;
  • IntelliJ IDEA version. It is recommended to use the same IntelliJ IDEA version that is used in the TeamCity build. TeamCity bundled an installation of IntelliJ IDEA. The version is written in the Inspections build log;
  • the set and versions of the IntelliJ IDEA plugins that the project relies on.