Qodana 2023.3 Help

Project tokens

Generally available paid linters require that you use the QODANA_TOKEN variable to provide a project token while running Qodana, for example:

qodana scan \ -e QODANA_TOKEN="<qodana-cloud-token>"
docker run \ -v $(pwd):/data/project/ \ -e QODANA_TOKEN="<qodana-cloud-token>" \ jetbrains/qodana-<linter>

The QODANA_TOKEN variable contains information that Qodana linters use for identification and verification. Based on this, Qodana establishes a connection with Qodana Cloud.

Below is the description of interaction between Qodana and Qodana Cloud once the connection is established.

License verification

The paid Qodana linters request and verify license information from a Qodana Cloud organization. If the verification step fails, the linter returns an error meaning that you cannot run it using the current license.

For example, you cannot run Qodana using an expired license. Nor can you run the Qodana for JVM linter using the Community license. To avoid this, you should obtain compatible and up-to-date licenses for each linter that you use.

Report collection

Additionally, your local Qodana report is bound with the project in Qodana Cloud. After binding, you can view actual Qodana reports in an aggregated and handy format, as well as keep a historical overview of older Qodana reports.

Once the project token is generated, you can regenerate or delete it as shown in the Manage a project section of the Qodana Cloud documentation.

Linters that require project tokens

Here is the list of linters that require project tokens:

This is the list of linters where project token usage is optional:

Without a project token, you will not be able to upload and study inspection results in Qodana Cloud.

Last modified: 28 February 2024