Nexus Repository Manager Plugin

The Nexus Repository Manager plugin allows engineers to surface build artifact and repository information directly within their Backstage entities. The plugin pulls data from Nexus and displays it contextually on the entity page, enabling teams to quickly locate, review, and validate stored artifacts without leaving Backstage.

With this plugin, users can:

View build artifacts stored in Nexus repositories in a dedicated Build Artifacts tab on the entity page.
Access repository metadata and artifact details without navigating to the Nexus web interface.
Link components in the Backstage catalog to Nexus repositories.

Configuring the Nexus Plugin in Venue.sh

To connect Nexus to Venue.sh, the following fields must be configured:

Field Required Description

Nexus Target URL ✅ Base URL for the Nexus instance (e.g., nexus.domain.com).

Field	Required	Description
Nexus Target URL	✅	Base URL for the Nexus instance (e.g., `nexus.domain.com`).
Authorization (Base64)	✅	Base64-encoded `user:pass` string for Nexus authentication. To locate, go to Nexus Settings > User Token > Access User Token, and copy the Base64 representation of `user:password`.
Target or Project Reference	✅	You must provide one of the following to identify the Nexus artifact data to display for each entity: Docker entity `nexus-repository-manager/docker.image-name`: Docker image name in Nexus, e.g., `group/artifact-name` To locate, find the asset within Nexus and copy the component name, including the group name and asset (e.g., `bitnami/redis-cluster`). Other entities (experimental) `nexus-repository-manager/repository`: The Nexus repository name, e.g., `releases` `nexus-repository-manager/name`: The specific artifact name, e.g., `my-service-api` To locate, find the asset within Nexus and copy the repository name (e.g., `bitnami-helm`) and component name (e.g., `redis-cluster`).

Authorization (Base64)

✅

Base64-encoded user:pass string for Nexus authentication.

To locate, go to Nexus Settings > User Token > Access User Token, and copy the Base64 representation of user:password.

Target or Project Reference

✅

You must provide one of the following to identify the Nexus artifact data to display for each entity:

Docker entity

nexus-repository-manager/docker.image-name: Docker image name in Nexus, e.g., group/artifact-name
To locate, find the asset within Nexus and copy the component name, including the group name and asset (e.g., bitnami/redis-cluster).

Other entities (experimental)

nexus-repository-manager/repository: The Nexus repository name, e.g., releases
nexus-repository-manager/name: The specific artifact name, e.g., my-service-api
To locate, find the asset within Nexus and copy the repository name (e.g., bitnami-helm) and component name (e.g., redis-cluster).

Follow these steps to configure the Nexus plugin:

In the Venue.sh app, click Plugins in the left-side navigation.
Find Nexus Repository Manager, then click Enable Plugin.
Enter the Nexus Target URL value.
Enter the Authorization (Base64) value.
Click Enable.

Nexus References (Entity YAML)

Once enabled, the following references are available:

Reference	Description
`nexus-repository-manager/docker.image-name`	Docker image name in Nexus, e.g., `group/artifact-name`.
`repository`	The Nexus repository name.
`name`	The specific artifact name.

Configuring the Nexus Plugin in Venue.sh​

Nexus References (Entity YAML)​

Configuring the Nexus Plugin in Venue.sh

Nexus References (Entity YAML)