Skip to content
This repository has been archived by the owner on May 1, 2019. It is now read-only.
Utsav Sanghani edited this page Sep 7, 2016 · 20 revisions

Documentation

Official Black Duck documentation:

https://github.com/blackducksoftware/integration-all

Release Notes:

1.4.2

*Issues Resolved

  • Failure conditions now work as expected.
  • The build number is now treated as a string instead of an integer.
  • The Risk report now shows which components violate a policy.
  • The CLI now requires an environment variable for the password.
  • When using Firefox version 45.x and clicking Save Configuration, you are now directed to a Save status dialog box.
  • When using Firefox versions 44.x and 45.x, clicking Test Connection now displays a status dialog box containing a Close button.

1.4.1

New Features

  • The level of logging is now configurable.

Issues Fixed

  • Login credentials are now encrypted in the Artifact build.properties files.
  • Risk counts containing more than four digits are now fully visible.
  • The risk report is now generated when a build is failed due to policy violations. If the build fails before the report has finished publishing, then the report is not generated.
  • In the Add Build Failure Condition options, there is now an option for product-specific build failure conditions.
  • Labels in the Risk Report UI are now updated.

1.4.0

New Features

Failure conditions based on the policy API support are now available:

  • You can configure the failure condition based on policy through the UI.
  • The build fails if there are any counts regarding policy violations.
  • The build logs the policy counts.
  • A version of the Hub that does not support the policy API logs that it is not compatible for the policy API.
  • The build passes even if the policy failure condition is not configured.

Issues Fixed

  • Addressed an issue wherein project scan failure conditions now wait for the Bill of Materials to be updated.
  • Addressed an issue wherein duplicate scan targets were not validated.
  • Addressed an issue wherein TeamCity builds were failing if the target already existed.
  • If an authenticated proxy server has been configured, then all communications from the plugin to Black Duck Hub are now done through the authenticated proxy server.
Clone this wiki locally