For more information regarding the options supported byĬov-build, refer to the Coverity documentation. This cov-build section is optional it is not automatically
In case of any errors returned by Coverity, the same would be returned The provided cov-build value is passed directly to cov-build without any value It provides the command line output fromĬov-build, including the options used and the skipped Note that the CLI skips filesystem capture options that are passed in withĬov-build. You can specify Coverity build options in the polaris.yml configurationįile by including options in a list or array. These are optional and not automatically generated by the CLI. See examples for language specific information.Īllows you to use Coverity options for cov-build, skipFiles and cov-configure. You must specify commands as they are entered in a command shell using commas A build capture requires the build and clean commands. Build Captureīuild capture means that Polaris observes your project as it is built, determining which Of capture available for each supported language. Tool and Client Support Compatibility and Support Information) shows types This the not a capture method.įor each version of Coverity, the Supported Platforms, Languages, and Compilers (under If enabled, it captures the current directory and that's treated as the projectĮnables the Coverity dynamic analysis for webapp security (project mode) or based on the file extension (source mode). If you already have a valid idir directory, code previously analyzed by CoverityĬan be captured and sent to Polaris for analysis.Ĭaptures by recursively searching for files under a specific project directory Polaris capture techniques NameĬoverity observes your project as it is built, determining which source filesĪllows users to explicitly tell Polaris the files to include. Note: At least one capture setting is mandatory for your ConfigurationĬoverity on Polaris captures files for analysis using the following techniques: Table 1.
0 kommentar(er)
