The work of analysis is done in three stages: capture, analyze, and commit. The stages are usually performed sequentially on the same machine. Here we describe each of these component steps, which you might want to configure independently to assist debugging and to support advanced use cases.
Capture
In this stage, Coverity captures a representation of your source code (whether compiled or file-based) and stores it in a known location, separate from the build artifacts. Coverity analysis does not modify source code or compiled binaries.
Analyze
During this stage, the developer or Dev/Ops uses the GUI, the CLI, or a script to scan binary representation of the code from the capture stage for issues or rule violations.
Commit
In this stage, analysis results are committed to the database (a collection of analysis instances corresponding to a release branch). The command or script that initiates the commit specifies the data-storage location, the connection information for the Connect server, and the user credentials.
Documentation Resources