Fork us on GitHub
×
Find plugins

Black Duck Hub2.1.1Minimum Jenkins requirement: 1.580.3ID: blackduck-hub

Usage

Plugin Information

Documentation

Official Black Duck documentation:

2.1.0 - https://github.com/blackducksoftware/hubintegrations-all/blob/master/Hub_Jenkins_Plugin_v.2.1.0.pdf

2.0.0 - https://github.com/blackducksoftware/hubintegrations-all/blob/master/Hub_Jenkins_Plugin_v.2.0.0.pdf

1.5.4 - https://github.com/blackducksoftware/hubintegrations-all/blob/master/Hub_Jenkins_Plugin_v1.5.4.pdf

1.5.3 - https://github.com/blackducksoftware/integration-all/blob/master/Hub_Jenkins_Plugin_v1.5.3.pdf

1.5.2 - https://github.com/blackducksoftware/integration-all/blob/master/Hub_Jenkins_Plugin_v1.5.2.pdf

1.5.1 - https://github.com/blackducksoftware/integration-all/blob/master/Hub_Jenkins_Plugin_v1.5.1.pdf

1.5.0 - https://github.com/blackducksoftware/integration-all/blob/master/Hub_Jenkins_Plugin_v1.5.0.pdf

1.4.1 - https://github.com/blackducksoftware/integration-all/blob/master/Hub_Jenkins_Plugin_v1.4.1.pdf

Preserving custom JAVA certificates

Required version: 1.5.3

The Hub Jenkins plugin works by downloading the scan client from your Hub instance. The client ships with its own JRE and at times the stock certificate may not be sufficient for your needs. If you are using custom certificates you can use the feature available in 1.5.3 to preserve the custom certs between Hub version upgrades and "propagate" your certificate to slave nodes.

The user will need to define a Jenkins environment variable in the Jenkins build that will contain the path to a certificate keystore file on the Jenkins slave where the build runs. The environment variable is: BDS_CACERTS_OVERRIDE

The environment variable can be set on master and can theoretically point to a common location that all slaves can access. Note: Generally slaves do not share drives with master, please sure make that all slaves can access the path of the keystore file.

Example is not a real path: BDS_CACERTS_OVERRIDE=/usr/var/tmp/cacerts

Please follow these steps to preserve the certificate before upgrading the plugin.

Step 1: Copy the existing certificate keystore file with the scan CLI for each slave For user’s running a version of the Jenkins plugin before upgrading to 1.5.3, they will most likely want to copy the keystore file that is in the scan cli directory on the slave. The will want to copy the file to another location on the Jenkins server in order preserve their imported SSL certificates for the scan cli to work with the Hub. The copied keystore file at the path defined by the environment variable BDS_CACERTS_OVERRIDE must have permissions to allow the user Jenkins is installed with to read the file in order to copy it.

Step 2: Configure the environment variable BDS_CACERTS_OVERRIDE for each slave In the Jenkins UI the user will add the environment variable to the slave. The value is the path on the slave where the keystore file was copied.

Step 3: Upgrade the plugin to at least version 1.5.3

Step 4: Execute a build job.

** Note: This can be configured before any builds are run to propagate the certificate to multiple slaves.

Release Notes:

2.1.0

  • Hub Jenkins now features the ability to set a configurable build state for failure conditions. 
  • Added functionality for Code Locations names.
  • Added functionality for cleaning up logs for successful scans.
  • Added functionality for directory exclusion patterns. 

2.0.0

  • Addressed an issue wherein scanning the Hub user interface using the Jenkins scanner may result in an illegal state exception.
  • Addressed an issue wherein testing a Hub connection may result in a exception error.
  • Fixed Proxy issues
  • Moved to Jenkins Marketplace
  • Please uninstall the existing (1.5.4 or below) after installing 2.0.0

1.5.4

  • Addressed an issue wherein Hub scans may fail and display an Unstable error message.
  • Improved performance with new functionality which enables you to select only your desired report sections prior to running reports.
  • Step API dependency is now for Step API versions 2.3 and higher.
  • Addressed an issue wherein the Test Connection procedure generated an incorrect error message.

1.5.3

  • Addressed an issue wherein the risk report risk report is updated to show which components violate a policy.
  • Hub server responses are now shown at the Global Configuration level.
  • Addressed an issue wherein an error for Scan Memory Allocation when under 256MB displayed an incorrect error message.
  • Pipeline plugin functionality is now supported.

1.5.2

  • Addressed an issue wherein integrations using the Black Duck Hub plugin were unable to establish a connection to internal Black Duck Hub installations during a scan.
  • Addressed an issue wherein Security Risk counts with more than four digits were not displaying correctly.
  • Fixed issues handling the cookies during authentication with the Hub.

1.5.1

  • A scan now creates a new version, even if that version already exists.
  • Migrating from a version 1.4.0 job configuration to a version 1.5.1 job configuration is now successful.
  • The level of logging is now configurable.

1.5.0

  • Initial open source release.
  • Updating to use the hub-common changes for public APIs.

1.4.1

  • Removed empty "BlackDuck Scan" configuration from the global configuration.
  • Using new CLI option to better check when the BOM has been updated with the scan results (Hub 3.0.0+ only).
  • Black Duck Failure Conditions are fixed; they are now added after the Black Duck Hub integration.
  • Failure Conditions now work even if the project name and version contain variables.
  • Failure Conditions now wait until the Bill of Materials is updated before checking the policy status.
  • The field Maximum time to wait for report (in minutes) is changed to Maximum time to wait for BOM update (in minutes).

1.4.0

  • Auto install of the BD Scanner (CLI).
  • Ability to pull a BOM report from Hub into Jenkins.
  • Fail the Jenkins build, if any component does not pass Hub policy (Hub 3.0.0+ only).
  • Network timeout for Hub connection configurable.
  • Update of plugin via Jenkins update site. ** Independent of Hub releases. ** Signaled in the Jenkins plugin management.

1.3.7

  • Fixed an issue wherein builds running on slaves log less messages to the console log, than when run on master.

1.3.6

  • Improves compatibility with non Oracle JREs.
  • Improves determination of the local hostname.

1.3.5

  • Fix an issue with Code locations being mapped to multiple projects (IJH-83).
  • Fix an issue with scanning >10 code locations in a single job (IJH-93).
  • Fix an issue where the build.JDK is set to < 1.7 (IJH-97).
  • Factored out common CI code for hub integrations.

1.3.4

  • Invalid URL succeeds in "Test Connection," but fails in the job run.
  • Make log directory option work with Hub 2.1.5, 2.2, and going forward.

1.3.3

  • Empty version never delivered.

1.3.2

  • Requires Java 1.7 or higher.
  • Fixed an issue where the command line interface login failed on Windows operating systems.

1.3.1

  • Fixed an issue where on a rescan the generation of the log file failed, the plugin displays the previously generated log file.
  • Fixed an issue where the incorrect port number was being passed to the Hub command line interface (CLI) when the Jenkins port value was null (no port number entered).

1.3.0

  • Initial release
ArchivesGet past versions
Labels
This plugin has no labels