JENKINS-74934: Display project references in OWASP dependency check table #156
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Display project references in OWASP dependency check table.
See JENKINS-74934 for more information.
Parse "dependency/projectReferences/projectReference" from the dependency-check XML, available in dependency-check.1.7.xsd through dependency-check.4.0.xsd (latest).
Then display the value in the Dependency-Check Reports table, and also make it filterable (searchable).
Testing done
Added test-case to verify that XML parsing works fine (see
ReportParserTest.testProjectReferences
)Deployed plugin to Jenkins installation and verified that the plugin works as intended.
Note that old jobs that were run with a previous version of the dependency-check plugin will not have the project references value populated in the table. It seems like the parsed Java objects are stored for historical jobs, rather than the original XML. However, new jobs will have value, as shown in the screenshot.
Also verified that the new table field is searchable (worked out of the box).
Submitter checklist
Screenshot