Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Click Tool Registry under Operations in Home page

  2. Click New Tool to add Coverity

3.Provide a Tool name and search for select Coverity under as Tool Identifier

...

4. Provide a description and click Create .

5. Click the connections tab in the Coverity In Tool Details of new Coverity tool, navigate to the Connections tab and provide URL, User name Username and Password.

...

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

...

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

...

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

...

9. Add the Select Coverity from the drop down to add and the tool and provide Credential name Coverity tool from the Tool drop down. Provide a Credential Name and Description for pipeline reference.

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

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

...

12.Provide the a unique step name (can be any) of your choice and choose the Tool Coverity Coverity in Tool drop down.

...

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

...

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 Pipeline to execute the Coverity Step.

...

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

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