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 5 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 a Tool name and select Coverity as Tool Identifier

4. Provide a description and click Create .

5. In Tool Details of new Coverity tool, navigate to the Connections tab and provide URL, Username and Password, upload the license file by clicking “Select Coverity License

6. Click Save. Navigate to usage Tab or another tab, then back to Connection tab. Click Test Connection to validate the connectivity. If tool connection is successful, you will receive the following messages:

7. Navigate to Tool Registry and choose the Jenkins tool associated with your pipeline.

8. In Accounts tab click “+ Register New Account Credentials”

9. Select Coverity from the drop down and the Coverity tool from the Tool drop down. Provide a Credential Name and Description for pipeline reference.

10. Navigate to Pipelines to add Coverity tool to pipeline for code scan.

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

12.Provide a unique step name of your choice and choose Coverity in Tool drop down.

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

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. Navigate to Summary view to validate the Coverity Console output.

21. Click the Console Log 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