In the event of an unexpected exception, each call to Dependency-Track is retried within an uniformly distributed, randomly generated period in the range of 50-500ms.
A warning is emitted when threshold values are configured but synchronous mode is disabled.
Add Support for Identification of Aliases ... by ignoring them (#168)
🐞 Bugs Fixed
The settings for the threshold values are now only visible when synchronous mode is enabled. This will hopefully avoid misunderstandings/misconfigurations.
Installation options
Using the CLI tool: jenkins-plugin-cli --plugins dependency-track:5.0.0
The connection test will also check server-side permissions for Dependency-Track v4.4 and newer (fixes #13)
🐞 Bugs Fixed
classic jobs with sync mode and no project ID used the looked-up ID in future runs, although they should not (fixes #98)
When using "New Findings" thresholds, the plugin is now looking for the latest succesful build with a report instead of just the previous build with the report. (PR #106)
The options "Dependency-Track project name" and "Dependency-Track project version" were only visible after saving and reloading the configuration page, although the global configuration "Auto Create projects" was set.
Fixed an issue with "Dependency-Track project" in classic (freestyle) jobs and Jenkins 2.319 LTS that caused the value to be "null" instead of empty, resulting in upload errors. Affected users should edit and save the job after updating to this plugin version.
Installation options
Using the CLI tool: jenkins-plugin-cli --plugins dependency-track:4.1.1
replaced inline JavaScript ... one step closer to compatibility with the CSP header
add 'min' values in field definitions of forms
uses modern div-layout for threshold level settings section
Clicking on the x-axis label (the job number) of the trend graph will take you directly to the full report.
added german translation
display report summary on build run page containing the number of severities found
🐞 Bugs Fixed
enforce Job/read permission in order to read the analysis results for a build run and the trend data on the project page
configured threshold levels in classic jobs where empty in the UI after saving them and reloading the config page. saving them again resulted in the deletion of previous none-empty values.
Installation options
Using the CLI tool: jenkins-plugin-cli --plugins dependency-track:4.0.0