> User Documentation Home

User Handbook
Tutorials
Resources

The following plugin provides functionality available through Pipeline-compatible steps. Read more about how to integrate steps into your Pipeline in the Steps section of the Pipeline Syntax page.

For a list of other such plugins, see the Pipeline Steps Reference page.

Synopsys Coverity plugin

View this plugin on the Plugins site

coverityIssueCheck: Check for Issues in Coverity View

  • coverityInstanceUrl (optional)

    Specify which Synopsys Coverity connect instance to check for issues.

    • Type: String
  • credentialsId (optional)

    Specify the credentials to use with the Synopsys Coverity connect instance.

    • Type: String
  • markUnstable (optional)

    If checked, will mark the stage Unstable but otherwise allow the pipeline to proceed instead of throwing an exception.
    As a byproduct, this also allows the step to return the issue count. Use returnIssueCount if you want to make this behavior more explicit.

    • Type: boolean
  • projectName (optional)

    Specify the name of the Coverity project the view is associated with.

    • Type: String
  • returnIssueCount (optional)

    If checked, will return the number of issues discovered in the specified Coverity view instead of throwing an exception.

    • Type: boolean
  • viewName (optional)

    Specify the name of the Coverity view that you would like to check for issues.

    • Type: String

withCoverityEnvironment: Inject Coverity environment into the build process

  • coverityInstanceUrl

    Specify which Synopsys Coverity connect instance to run this job against.

    • Type: String
  • configureChangeSetPatterns (optional)
      Nested Object
    • changeSetExclusionPatterns

      Specify a comma separated list of filename patterns that you would like to explicitly excluded from the Jenkins change set.
      The pattern is applied to the $CHANGE_SET environment variable, and will affect which files are analyzed in an incremental analysis (cov-run-desktop).
      Examples:

      File Name Pattern Will be excluded
      test.java *.java Yes
      test.java *.jpg No
      test.java test.* Yes
      test.java test.???? Yes
      test.java test.????? No
      • Type: String
    • changeSetInclusionPatterns

      Specify a comma separated list of filename patterns that you would like to explicitly included from the Jenkins change set.
      The pattern is applied to the $CHANGE_SET environment variable, and will affect which files are analyzed in an incremental analysis (cov-run-desktop).
      Examples:

      File Name Pattern Will be included
      test.java *.java Yes
      test.java *.jpg No
      test.java test.* Yes
      test.java test.???? Yes
      test.java test.????? No
      • Type: String
  • createMissingProjectsAndStreams (optional)
    • Type: boolean
  • credentialsId (optional)

    Specify the credentials to use with the Synopsys Coverity connect instance.

    • Type: String
  • projectName (optional)

    Specify the name of the Coverity project.
    The resulting project name is stored in the $COV_PROJECT environment variable, and will affect both the full and incremental analysis.

    • Type: String
  • streamName (optional)

    Specify the name of the Coverity stream that you would like to use for the commands.
    The resulting stream name is stored in the $COV_STREAM environment variable, and will affect both the full and incremental analysis.

    • Type: String
  • viewName (optional)

    Specify the name of the Coverity view that you would like to check for issues.
    The resulting view name is stored in the $COV_VIEW environment variable, and affects checking for issues in both the full and incremental analysis, if configured.

    • Type: String

Was this page helpful?

Please submit your feedback about this page through this quick form.

Alternatively, if you don't wish to complete the quick form, you can simply indicate if you found this page helpful?

    


See existing feedback here.