The CLM Book - Optimized Component Lifecycle Management with Sonatype CLM

14.2. Global Configuration

After a successful installation of Sonatype CLM for Hudson and Jenkins, a new option will be available in the Jenkins/Hudson management area, Configure Sonatype CLM for CI. Follow these instructions to configure Jenkins or Hudson to connect to your Sonatype CLM Server.

Figure 14.2. Global Configuration of Sonatype CLM for CI in Jenkins

Sonatype CLM server settings (required)

Server address

This is the address for the Sonatype CLM server as it can be reached from the Jenkins/Hudson server. By default, the Sonatype CLM Server address is http://localhost:8070.

If your Sonatype CLM server is behind a proxy server for serving HTTPS or other reasons, you have to use the public URL as it is reachable from the continuous integration server. Only the master Jenkins/Hudson server connects to the CLM server and you therefore only need to ensure connectivity in terms of open firewall ports and proxy server settings between the master CI server and the CLM server.

Username

This is the username you wish to use to connect to the CLM Server. Since these settings will be used across all projects for your Jenkins/Hudson installation, we suggest creating a single account on the Sonatype CLM Server for Jenkins/Hudson, and then associating that account with the Application Evaluator role for the Organizations or Applications you will be linking to Sonatype CLM for Hudson/Jenkins.

Password

The password for the username entered above.


	Username and password can also be configured per job.

Global mask options

Anonymize paths: Enabling this feature will anonymize all paths before data is sent to the Sonatype CLM server. Ultimately, this prevents the CLM report from reporting the locations/occurrences of components.

Global path options

Scan targets: The scan targets setting allows you to control which files should be examined. The configuration uses an Apache Ant styled pattern, is relative to each project’s workspace root directory, and has a useful default setting that includes all jar, war, ear, zip and tar.gz files. The default value is therefore

**/*.jar, **/*.war, **/*.ear, **/*.zip, **/*.tar.gz


	This default only applies if, and only if, neither global nor job config specify scan targets. Adding to this, if you are using a private Maven repository, our default pattern will include your entire Maven repo. This could greatly increase the time necessary for your evaluation, as well as skew evaluation results. To avoid this, consider using a more specialized pattern like */target/.jar.

Module excludes: If you are using Sonatype CLM for Maven, you may have noticed the creation of module information files. The process for excluding modules is documented in the Excluding Module Information Files in Continuous Integration Tools section of the Sonatype CLM for Maven chapter.
Advanced options: A number of additional parameters can be supplied to the plugin using this input field. Typically these parameters will be determined by Sonatype support.