Opsera now offers Git Scraper support in a pipeline step. This allows user to choose from scraper libraries then run a scan against the configured SCM repos. Define a maximum threshold and pipeline will use the values to determine the final status of the step. Use the following documentation as a guideline of how to use Opsera’s Git Scraper support in pipelines.
| Table of Contents | ||||
|---|---|---|---|---|
|
Git Scraper Pipeline Configuration
...
In Pipeline Logs, click the ‘Report’ row. In the following screenshot, the results exceeded the threshold number provided in the step configuration.
View the Git Scraper Execution Summary. The threshold provided for this scan was 0 There are 3 results appearing in the result below. Since the number of results did not meet the threshold, the step had a ‘Failure’ status.
Git Scraper KPI
View Git Scraper metrics from scans using the Git Scraper Metrics KPI in Insights. The metrics provide the number and trend result (compared to last scan) of Scanned Repositories, Clean Repositories, and Total Number of Issues. The Last Scan results are also included.
...
Scanned Repositories - The number of scanned repositories in the provided date range.
Clean Repositories - The number of clean repositories in the provided date range.
...
Total Number of Issues - The number of issues existing in the provided date range.
...