In the deployment example just described, all code analysis is performed centrally on the build server. The following deployment example augments the previous example by adding Coverity Analysis to the developer's machine. This deployment supports a workflow like the following:
Coverity Analysis is installed on a build server where the artifacts of the build are analyzed.
At the conclusion of each build-and-analysis run, which happens daily or whenever code is checked in, code issues that have been discovered are committed to Coverity Connect as issues.
Developers use their clients to browse the Connect server and review issues that have been assigned to them.
The developer performs analysis locally, and resolves issues.
The developer checks in fixed code.
The central build also runs an analysis to discover issues that arise from the code's interaction with other checked-in code.
The developer resolves any additional issues discovered in the central analysis and checks in code again.
To support this model, the Code Sight or Coverity Desktop plug-in is installed in the developer's IDE, allowing the developer to find, examine, fix, and analyze code directly in the IDE.