Coverity Setup Considerations

These are the main issues you should be aware of if you are responsible for setting up Code Sight to run Coverity Analysis.

• If Polaris is your server:

  The server itself requires no extra configuration. A client system might require some special configuration. If so, we strongly recommend that all systems used by a team have the same configuration settings. See Configure Coverity Analysis to Use Polaris.

• If Coverity Connect is your server:

  Each client system should have a coverity.conf file to specify the host and the active Coverity Connect stream.

  Typically, coverity.conf is created when you install Code Sight and Coverity Analysis. For some client configurations, you might need to add or adjust the settings in coverity.conf. See Configure Coverity Analysis to Use Coverity Connect.

  Preparing the Coverity Connect server: Each Coverity Connect server must provide a license file and the installers for downloading and installing Coverity analysis tools on various platforms. See Preliminaries: Server-side Configuration for Coverity Connect.

• If you plan not to use a server:

  You can also run local Coverity (SAST) scans of your source code, without connecting to the Internet. Instructions for installing Code Sight on a disconnected (or air-gapped) system are provided in each installation guide.

• Special-purpose configurations:

  Some setups might need additional configuration settings before you run Code Sight. For more details, see the Administration section.