Qodana for JVM Docker image configuration

Directories

Profile

Qodana profile can be configured using these CLI options. Alternatively, you can configure Qodana using the qodana.yaml file as described in the Configure profile section.

Baseline

To learn more about the baseline feature, see the Run in baseline mode example, or study the Baseline section.

Miscellaneous

Qodana Cloud

Override the default inspection profile

If no profile is specified, the default qodana.recommended profile is used. For more options of how to specify a profile, see Order of resolving a profile. For more about available profiles, see Set up a profile.

Save a report as HTML

By default, the HTML report is stored in a separate report/ subdirectory under the results directory. This location could be configured with --report-dir.

Display a report in HTML

After the inspection is finished, the container will not exit and will listen on port 8080. You can connect to http://localhost:8080 to see the results. To stop the web server, press Ctrl-C in the Docker console.

Change the Heap size

By default, Heap size is set to 80% of the host RAM.

Log INFO messages to STDOUT

The default log level for STDOUT is WARN.

Provide different Gradle settings

Use a different 'idea.properties' file

Turn off user statistics

To disable the reporting of usage statistics, adjust the idea.headless.enable.statistics value:

Manage plugins

You can add any free IntelliJ platform plugins or your custom plugin by using the following command:

To optimize the most common cases, some bundled plugins are disabled by default. You can check the whole list of disabled plugins in /root/.config/idea/disabled_plugins.txt.

The Java, Kotlin for Server Side, their libraries'/frameworks', Gradle, and Maven The Java, Kotlin for Server Side, their libraries'/frameworks', Gradle, and Maven plugins are enabled by default. plugins are enabled by default.

To change the plugins list, do any of the following:

• Override disabled_plugins.txt by mounting your own file:

  docker run ... -v $empty_file$:/root/.config/idea/disabled_plugins.txt \ jetbrains/qodana-jvm

• Use IDE properties idea.required.plugins.id and idea.suppressed.plugins.id:

  docker run ... jetbrains/qodana-jvm \ --property=idea.required.plugins.id=JavaScript,org.intellij.grails \ --property=idea.suppressed.plugins.id=com.intellij.spring.security

Analyze changes

Qodana for JVM lets you check only changed files:

You can adjust the idea.required.plugins.id value and keep only the VCS plugin suitable for your project.

Run in baseline mode

In baseline run mode, each new Qodana for JVM run is compared to some initial run selected as a "baseline". This can help in situations when you have no possibility to fix old problems and rather want to prevent the appearance of new ones.

where <baseline-path> is the path to a qodana.sarif.json file from an earlier run. If the --baseline-include-absent option is provided, the inspection results will include absent problems, that is the problems detected only in the baseline run but not in the current run.

After the inspection is finished, Qodana for JVM displays the summary of the current project state compared to the baseline.

where the detected problems are aggregated as follows:

• new: The problem was detected only in the current run but not in the baseline run.

• absent: The problem was detected only in the baseline run but not in the current run.

• unchanged: The problem was detected both in the current run and in the baseline run.

The SARIF output report will contain the per-problem information on the baseline state.

Set a quality gate

Qodana for JVM lets you configure a "quality gate", that is, the number of problems that will act as a threshold. If the threshold number is reached, the inspection run is terminated.

When running in baseline mode, a threshold is calculated as the sum of new and absent problems. Unchanged results are ignored.

Run as non-root

By default, the container is run as the root user so that Qodana for JVM can read any volumes bind-mounted with the project and write the results. As a result, files in the results/ folder are owned by the root after the run.

To avoid this, you can run the container as a regular user:

Note that in this case the results/ folder on host should already be created and owned by you. Otherwise, Docker will create it as root and Qodana for JVM will not be able to write to it.

Cache dependencies

You can decrease the time for a Qodana for JVM run by persisting cache from one run to another. For example, package and dependency management tools such as Maven, Gradle, npm, and Yarn keep a local cache of downloaded dependencies.

By default, Qodana for JVM would save caches to folder /data/cache inside container. This location could be changed via --cache-dir cli argument. The data inside is per-repository, so you can pass cache from branch-a to build checking branch-b. In this case, only new dependencies would be downloaded, if they were added.

Example for local run:

In this case mapping the same <cache-directory> would speed up the second run.

In a GitHub workflow you can utilise actions/cache, see full example.

GitLab CI/CD also has cache which can be stored only inside the project directory. In this case, we recommend excluding the cache folder from inspection via qodana.yaml.

Override the default run scenario

You can override the standard Qodana run scenario by using the --script option. By default, Qodana employs the default scenario, which is equivalent to running: