Nexus Sonatype

The Nexus Sonatype source type component supports granular access and filtering for artifacts stored in Nexus repositories.

To use Nexus as an artifact source, select Nexus Sonatype from the Source Config Type list and then specify its properties. For more information about creating components, see Create components.

Compatibility with Deployment Automation

The Nexus Sonatype source config type relies on the following parameters:

Supported editions OSS and Professional
Supported versions Nexus 3.x
Certified repository types Maven, Raw, and NuGet.

Note: Other repository types might work, but their functionality has not been tested.

Back to top

Nexus fields table

The following table describes the properties fro the Nexus Sonatype source configuration type.

Field Description
Server URL (Required) Base URL and port for the Nexus server, for example, http://localhost:8081.
User Name Nexus user name.
Password Nexus user password.
Repository (Required) The name of the Nexus repository.
Nexus Component The name of the Nexus component. This option enables you to import versions of that component only. Use it when you have multiple Nexus components in the same repository, for example, for NPM repositories.
Component Group The group ID of the component to which the assets belong. In Maven repositories the ID follows Java package naming rules, for example, org.apache.maven.
Import folders as versions Applies to repository types that do not have specific versions, for example, 'raw'. This option enables you to import directories with subfiles as separate versions.
Import all new versions If this option is selected, all the missing versions will be imported. Otherwise, only the latest version is imported.
Skip empty versions If this option is selected, versions without content are not imported.
Include files

Specify patterns to match files that you want to include in the upload. You can match exact file paths and file names, or you can specify wildcards. The default value is **/* for directories/files.

You can enter exact file path and file name combinations with one entry per line, for example:
Maestro/RLM.jobs
Maestro/RLM.sched

You can also specify wildcards to match directories and files, where the wildcard ** indicates every directory and the wildcard * indicates every file. For example, the pattern dist/**/* retrieves the entire file tree under the dist directory.

Exclude files Specify patterns to match files that you want to exclude from the upload. You can match exact file paths and file names, or you can specify wildcards. See the earlier Include files examples.
Preserve execute permissions If this options is selected, file execute permissions are preserved.
Import versions automatically

This option enables you to set periodic imports. Deployment Automation will automatically poll for new versions based on the Quiet Period and Polling Period.

The Quiet Period indicates the time (in minutes) during which there's no polling, and it starts after the last polling period that detected changes.

The Polling Period indicates the time between polls (in seconds).

For example, with Quiet Period set to 60 and Polling Period set to 300, Deployment Automation will poll for new versions every 300 seconds. After detecting and importing changes, it will pause polling for 60 minutes.

Copy to CodeStation

This option creates a tamper-proof copy of the artifacts and stores them in the embedded repository called CodeStation.

The option is selected by default. For optimal use of Deployment Automation, ensure that the option remains selected.

If you clear the Copy to CodeStation option, Deployment Automation will save pointers to versions rather than the versions themselves. This enables you to track versions and save space on your Deployment Automation server but limits your ability to download individual versions.

For details on maintaining versions in external sources, see Maintain versions externally.

Use latest component properties for versions download When downloading component version artifacts, Deployment Automation uses the properties set for the associated component instead of the properties set when the version is created.

Note: Component version properties are always preserved when a version is created.
Default Version Type (Required) The default version type to be created for imported versions.
Inherit cleanup cettings If this option is selected, the environment will inherit version cleanup configurations from the settings of each component or the system.

Back to top

See also: