For the complete documentation index, see llms.txt. This page is also available as Markdown.

Nexus connector settings reference

This topic provides settings and permissions for the Nexus connector.

This topic provides settings and permissions for the Nexus connector.


What you will learn from this topic

  • Nexus permissions: How to assign the permissions the Nexus account associated with the connector needs.

  • Artifact type support: Which artifact types the Nexus connector supports.

  • Nexus Artifact Server settings: How to configure the connector itself, including the repository URL, version, and credentials.

  • Nexus Artifact Details settings: How to point a pipeline artifact source at a specific repository, path, and tag in Nexus.


Nexus permissions required

The user account associated with the connector must have the following permissions in the Nexus server:

  • Repo: All repositories (Read)

  • Nexus UI: Repository Browser

  • If using Nexus 3 as a Docker repo, the account also needs a role with the nx-repository-view-*_*_* privilege.

Nexus repository permissions in the Nexus server

For more information, go to the Sonatype documentation on Managing Nexus security.


Artifact type support

The following table lists which artifact types the Nexus connector supports.

Legend:

  • M - Metadata. This includes Docker image and registry information. For AMI, this means AMI ID-only.

  • Blank - Not supported.

Docker Image(Kubernetes/Helm)

AWS AMI

AWS CodeDeploy

AWS Lambda

JAR

RPM

TAR

WAR

ZIP

PCF

IIS

M

M

Docker support

Nexus 3 artifact servers only.


Nexus artifact server settings

The Harness Nexus artifact server connects your Harness account to your Nexus artifact resources. It has the following settings.

Name, description, and tags

The unique name for this connector.

Harness creates an Id (Entity Identifier) based on the name. You can change the Id while creating the connector. Once saved, the Id cannot be changed, but you can change the Name.

Description and Tags are optional.

Nexus repository URL

The URL that you use to connect to your Nexus server. For example, https://nexus3.dev.mycompany.io/repository/your-repo-name.

Nexus Repository URL setting on the connector

Version

The supported Nexus version, 3.x.

For Nexus 3.x, Harness supports only the Docker repository format as the artifact source.

Credentials

The username and password for the Nexus account to use for this connector.

For the password, select a Harness text secret.


Nexus artifact details settings

Configure the following settings to point a pipeline artifact source at a specific artifact in Nexus.

Repository URL

The URL you would use in the Docker login to fetch the artifact. This is the same as the domain name and port you use for docker login hostname:port.

Repository port

The port you use for docker login hostname:port.

As a best practice, include the scheme and port. For example, https://your-repo:443. If you cannot locate the scheme, you may omit it. For example, your-repo:18080.

For more information, go to the following Sonatype documentation:

Repository

Name of the repository where the artifact is located.

Artifact path

The name of the artifact you want to deploy. For example, nginx, private/nginx, or public/org/nginx.

The repository and artifact path must not begin or end with /.

Artifact Path setting on the artifact source

Tag

Select a tag from the list.

Last updated

Was this helpful?