Sonatype Nexus

Upload resources into Sonatype Nexus Repository 3 hosted helm, maven2, npm and raw repositories during transfer, with credentials and overwrite rules.

The nexus.uploader.transfer.config.ocm.software/v1alpha1 uploader uploads the resources it matches into one Nexus hosted repository during transfer. Each repository format has its own page below with a complete configuration.

Repository types

FormatGuidePublished access
helmUpload Helm ChartsHelm/v1
maven2Upload Maven ArtifactsWget/v1
npmUpload npm PackagesWget/v1
rawUpload Raw FilesWget/v1

At upload time the uploader reads the format from the server with GET <url>/service/rest/v1/repositories/<repository>.

Unsupported repositories

RepositoryErrorAlternative
pypi and other formatshas format "pypi"; supported: helm, raw, maven2, npmUpload with the format’s own client
Proxy or group repositoriesuploads need a hosted repositoryUpload into the hosted repository behind it

Prerequisites

  • OCM CLI installed
  • A component version in a CTF or OCI repository
  • A Nexus hosted repository
  • A user that may upload into the repository and read its settings

Configure credentials

The uploader resolves credentials for the HelmChartRepository identity of <url>/repository/<repository>, falling back to its Wget identity. A Wget consumer without a path covers every repository on the server:

type: generic.config.ocm.software/v1
configurations:
  - type: credentials.config.ocm.software
    consumers:
      - identity:
          type: Wget
          hostname: nexus.example.com
          scheme: https
        credentials:
          - type: WgetCredentials/v1
            username: <USERNAME>
            password: <PASSWORD_OR_USER_TOKEN>

hostname is the bare host name. A value such as https://nexus.example.com matches no request, so the upload is sent without credentials and fails with 401.

Existing files at the upload path

Nexus records no owner of a file, so the uploader never replaces stored content:

  • raw and maven2: a stored file is never overwritten, even when the repository allows redeploys. Same content is reused; different content fails the transfer.
  • helm and npm: Nexus stores them under a path derived from the package. A stored package with the same content is reused. Different content under the same name and version fails when the repository disallows redeploys.

Troubleshooting

Symptom: failed detecting the type of … repository …: GET … returned status 401

Cause: No credentials were found for the server, so the uploader asked anonymously.

Fix: Configure credentials as shown above, with the bare host name in hostname.

Symptom: failed detecting the type of … repository …: GET … returned status 403

Cause: The user may deploy but not read the repository settings.

Fix: Grant read access to the repository configuration, or use a user that has it.

Symptom: nexus repository … already stores a different file at …; the uploader never overwrites files in … repositories

Cause: The raw or maven2 repository already stores a file with different content at the upload path, for example from another component version with the same resource version.

Fix: Configure a path that is unique for the resource, or remove the stored file.

Upload Helm Charts to Sonatype Nexus
Upload Helm chart resources into a Sonatype Nexus helm hosted repository during transfer and publish them as Helm/v1 access.
Upload Maven Artifacts to Sonatype Nexus
Upload a JAR and its POM into a Sonatype Nexus maven2 hosted repository during transfer, so that Maven resolves the artifact.
Upload npm Packages to Sonatype Nexus
Upload npm package resources into a Sonatype Nexus npm hosted repository during transfer, so that npm install finds them.
Upload Raw Files to Sonatype Nexus
Upload any resource as a plain file into a Sonatype Nexus raw hosted repository during transfer and publish it as Wget/v1.