Sonatype CLM for Hudson and Jenkins

Chapter 3. Global Configuration

After a successful installation of Sonatype CLM for Hudson and Jenkins, the global Jenkins/Hudson configuration menu, displayed in Figure 2.1, “Jenkins Global Configuration Menu” includes a separate item for Sonatype CLM with the title Configure Sonatype CLM for CI . Click the link to get to the global configuration displayed in Figure 3.1, “Global Configuration of Sonatype CLM for CI in Jenkins”.

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

The global configuration for Sonatype CLM for CI is used as the default configuration for all invocations of the plugin. Specific parameters supplied for individual jobs are appended to the global configuration. You can configure the following settings:

Sonatype CLM server settings

Server address: The address for the Sonatype CLM server as it can be reached from the Jenkins/Hudson server. The address should be the same one a user is using to access the Sonatype CLM server interface. A suitable URL for a default install on your local computer would be 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. This configuration parameter is the only required setting.

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. Our recommendation is to leave this disabled, unless you are worried about Sonatype knowing about the file names of your 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 Guide.

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.