Use this information to resolve common Coverity errors that can occur when Bridge CLI runs scans against a Coverity Connect deployment.
These errors can occur when the Coverity analysis method selected by Bridge CLI does not match the target Coverity deployment, or when the required Coverity analysis tools are not available.
Bridge CLI determines the Coverity analysis method by the coverity.local setting:
-
When
coverity.local=false(default), Bridge CLI uses the thin client. Capture runs locally and analysis runs remotely using scan services. -
When
coverity.local=true, Bridge CLI uses the full analysis client. Both capture and analysis run locally.
| Error | Cause | Solution |
|---|---|---|
ERROR: Failed to retrieve tool information details Fetch tool information: received unexpected response status code '500' from Connect API |
Bridge CLI attempts to use the thin client, but the target Coverity Connect deployment does not have scan services enabled. Because scan services are not available, the server cannot provide the thin client tools that Bridge CLI is trying to download and use. |
Set |
ERROR: Download descriptor for Coverity tool were not found in the Coverity Connect server: https://coverity.server.com |
Bridge CLI is configured to use the full analysis client. Bridge CLI attempts to download the full analysis client from the Coverity Connect server. If the required installers are not available, the download fails. |
To resolve this issue, use one of the following options:
|