For Coverity, Code Sight version 2025.10.0 adds support for the Coverity CLI.
Enhancements
-
When you add a new scan configuration for Coverity Analysis, you can choose how scan code.
-
If you choose Coverity (.yaml, .json), then Code Sight scans code by using the
Coverity CLI.
In this case, it finds configuration settings in a local configuratio file, which can be in either YAML or JSON format.
This enhancement is available in JetBrains IDEs (including IntelliJ), Visual Studio, and VS Code.
Using the Coverity CLI is now the recommended method.
-
If you choose Coverity (.conf), then Code Sight continues to scan code by using the
cov-run-desktopcommand.In this case, Code Sight continues to use the legacy configuration file format, coverity.conf.
Remember: Support for scanning a single file is available from Coverity 2024.6.0 onwards. -
If you choose Coverity (.yaml, .json), then Code Sight scans code by using the
Coverity CLI.
Discontinued support
Support for the following Black Duck product versions has been deprecated, and will be discontinued in a future release of Code Sight:
-
Polaris users:
You must upgrade Code Sight to version 2025.4.0 or a later version by September 15, 2025. Failure to upgrade will result in an inability to interact with Polaris.
For more information, please see [ANNOUNCEMENT] Reminder - Polaris API Deprecations and Important Due Dates for API and Bridge Upgrade Requirements.