DEV Community

Grégoire Willmann for Kinoba

Posted on • Originally published at Medium

Dependencies Check with Jenkins

The wonderful OWASP Dependency-Check Jenkins plugin has recently published an update introducing breaking changes for my pipelines.
So I have written a quick guide on how to upgrade your pipelines to fix those:

Original article here:

After upgrading the plugin, create a new Dependency-Check installation in the Global tools configuration of your Jenkins instance:
new installation of Dependency-Check

We have a Jenkins job running every day which sole purpose is to update the NVD database.
As it was not a pipeline job we had to reconfigure it from the UI.

This job runs every day at 4 AM

Next we had to change all our pipeline script for checking and publishing results of dependencies checks:

  • Checking

Changed from

dependencyCheckAnalyzer datadir: ‘/home/jenkins/security/owasp-nvd/’, hintsFile: ‘’, includeCsvReports: false, includeHtmlReports: true, includeJsonReports: true, includeVulnReports: true, isAutoupdateDisabled: true, outdir: ‘build/owasp’, scanpath: ‘’, skipOnScmChange: false, skipOnUpstreamChange: false, suppressionFile: ‘’, zipExtensions: ‘’


sh(‘mkdir -p build/owasp’)
dependencycheck additionalArguments: ‘ — project [project_name]— scan /home/jenkins/security/owasp-nvd/ — out build/owasp/dependency-check-report.xml — format XML — noupdate’, odcInstallation: ‘Dependency Checker’
  • publishing results

Changed from

dependencyCheckPublisher canComputeNew: false, defaultEncoding: '', healthy: '', pattern: 'build/owasp/dependency-check-report.xml', unHealthy: ''


dependencyCheckPublisher pattern: 'build/owasp/dependency-check-report.xml'

Top comments (0)