TeamCity
 
3.0
You are viewing the documentation for an earlier version of TeamCity.
  1. TeamCity Documentation
  2. UI Reference
  3. Administration
  4. Create Edit Build Configuration
  5. 3.Build Runners
  6. Inspections

Inspections

Last modified: 20 April 2023

This page contains reference information about the Inspections Build Runner fields. This runner is intended for gathering inspection results in the IntelliJ IDEA or Maven2 projects.

Option

Description

Build runner

Select Inspections from the drop-down list. This runner is used for gathering IntelliJ IDEA inspections results.

Additional Pre Processing (Ant)



Option

Description

Run before build

In the appropriate fields, enter the Ant scripts and targets (optional) that you want to run prior to starting the build. The path to the Ant file should be relative to the project root directory.

Inspections Parameters



Option

Description

Inspections profile path

Use this text field to specify the path to inspections profiles file relative to the project root directory. By default, the profile path is specified in the IntelliJ IDEA project file *.ipr, and the field is left blank. Use this field, if you want to override project profile mapping.

Inspections profile name

Select the name of the desired shared profile from the combo box. By default, the name is unspecified, which means that project modules will be inspected according to their own settings.

Errors limit

Fail build if specified number of errors exceeded. By default first error that occurs will fail the build.

Warnings limit

Fail build if specified number of warnings exceeded. Leave blank if there is no limit.

tip

If you need to restrict the sources scope on which to tun the Inspections runner, you can specify additional JVM paramenters (in the JVM command line parameters field).

Example:

-Didea.exclude.patterns=testData/**;testdata/**;help/**;test/**;maverick/**;src/tips/**;[testData]/**
-Didea.include.patterns=testData/tables/**

  • all patters must end with either ** or * (this effectively limits the patterns to only the directories level, they do not support file-level patterns)

  • includes have precedence over excludes

  • references to modules can be included as [module_name]/<path_within_module>

  • "include" pattern has a special behaviour (due to underlying limitations): it includes the directory specified and all the files residing directly in the directories above the one specified. (in the example above, testData/basicTest.xml file will be included into the analysis)