Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Integrate Coverity scan to Opsera pipeline as a security gate.

Note: Coverity is a licensed tool and please open an support Jira request as it requires work from our end to add your license to enable the integration.

Configuring Coverity to Tool Registry:

  1. Click Tool Registry under Operations in Home page

  2. Click New Tool to add Coverity

3.Provide Tool name and search for Coverity under Tool Identifier

4. Provide description and click Create .

5.Click the connections tab in the Coverity and provide URL, User name and Password.

6.Click Save and go to usage Tab and come back to Connection tab to click Test connection to validate the connectivity

7.Go to Tool Registry and choose the Jenkins associated to your pipeline

8.Click the Accounts Tab and click “+ Register New Account Credentials”

9.Add the Coverity from the drop down to add the tool and provide Credential name and Description for pipeline reference.

10. Click Pipelines to add Coverity to pipeline for code scan

11.Open any pipeline and Click workflow ->Edit Workflow → click + icon to add Coverity step

12.Provide the step name (can be any) and choose the Tool Coverity

13. Click Save and Click the Setting wheel icon to add the Coverity Configurations from Tool Regsitry

14. Choose the Jenkins tool associated to Coverity Tool

15. Add the Coverity tool and credentials from the Drop down

16.Provide the Coverity Stream Name

17.Choose the SCM Account , Repository and Branch that needs to scanned part of the pipeline

18.Click Save and exit the Step configuration form.

19.Click Start pipeline to execute the Coverity Step

20. Go to Summary view to validate the Coverity Console output.

21.Click the Console Output to view the logs.

22.Click the X on top of the screen to go to the summary view to validate other stages in the pipeline.

  • No labels