OSS To community edition upgrade help

Community Announcements News
, ,
1

Hi Team,
We are currently using OSS Nexus version 3.75.1 and are planning to upgrade to the latest Community Edition. Could you please provide the location of the Helm charts and the container images for version 3.77.1? Additionally, we would appreciate it if you could share the minimum PostgreSQL requirements for this version.

Regards,
Kiran

2

Hi, Kiran,

Helm chart/container images for Nexus Repository can be found on our downloads page.

As for your Postgres server, you’ll need version 14 or newer.

3

Thank you for your response, Jonathan.

I could see helm chart with postgreSQL only. we are using 3.75 with H2 DB. post upgrade to 3.77.1 will upgrade the DB will that works ? or we need to follow the below steps

  1. Take backup of nexus-data folder from the running pod.
  2. Shutdown the nexus (3.75.1) and install the nexus (3.77.1) with new helm chart.
  3. Once POD up & running, delete the folder nexus-data and replace the backup folder taken in step1.

Please correct me if this works.

4

Kiran,

If you’re trying to migrate databases as well, you’ll need to follow the instructions here in our documentation.

It is not recommended that you try to upgrade versions and migrate databases in the same motion.

5

Hi Jonathan,

After evaluating the Community Edition, we found that it does not align with our technical and operational needs. As a result, we are considering Nexus OSS as a more suitable option.

I came across the conversation below and understood that the source code is available for Nexus OSS.
If I build the image locally using the latest available source code (e.g., version 3.80.x), could you please confirm which Helm chart I should use for deploying it?

  • Are there any known limitations or hard caps in OSS latest versions (ex, version 3.80.x) ?
  • Does the latest OSS release support integration with an external database, or is it still limited to the embedded one?

Appreciate your guidance on this.

Changes to Nexus Repository Core codebase - Sonatype Nexus Repository - Sonatype Community

6

Hi, Kiran,

Database support
The open-source codebase only supports the embedded database.

Helm charts
The only Nexus Repository Helm chart Sonatype provides is our HA/Resiliency chart, which requires an external PostgreSQL database. As a result, it’s not suitable for deployments using the open-source codebase.

Hard caps
There are no usage caps when you build using the open-source codebase.

7

Hi Jonathan,
Thank you for the reply.
We have built the package using the OSS source code and installed it on a local machine. However, we observed that not all repository formats are available, only Maven, Raw, and APT are listed. Please refer to the attached screenshot for reference.

Additionally, although we installed version 3.81, the UI displays **Core instead of the expected version number in the Sonatype logo. Is this behavior expected? If so, could you guide us on how to update or display the correct version?

Furthermore, we are planning to upgrade from version 3.75 to 3.81. Could you clarify what will happen to existing repositories (e.g., PyPI, YUM, RubyGems, NPM, etc.)? As per the current UI, it does not appear to support creating repositories in these formats.

Could you confirm if this limitation is expected in the OSS version, and what options are available to enable these formats post-upgrade?

The features not available in OSS latest version
Repair tasks for all formats which are available in 3.75
Rut auth and realms
Clean-up policy for all format of repos

image
image742×637 34.6 KB

I would appreciate it if you could share any official documentation or guidance to resolve the missing features mentioned above. Without a fix, we may not be able to proceed with upgrading from version 3.75 to the latest OSS version.

If this is expected behavior, it appears that the OSS version of Nexus now includes limited repository formats and capabilities. In that case, please confirm whether using the Community (OSS) edition restricts these features by design, and if a Pro or licensed version is required to enable full functionality.

8

Hi, Kiran,

What you’re seeing is intended. The open-source codebase includes just Maven, Raw, and APT repositories. Other repository formats aren’t officially supported with the open-source codebase, and it doesn’t have the repair task or support for user tokens.

I think there’s some confusion about versions of Nexus Repository. There are three:

  • Our open-source codebase (that we call “Core” and that you’ve referred to as “OSS”) is something you build yourself, comes at no cost to you (the user), and has three repository formats.
  • Community Edition has more features and repository formats, comes at no cost to you (the user), but has usage limits.
  • Pro Edition has even more features, comes at a cost, and has no usage limits.

Check out the feature difference between Community Edition and Pro in our documentation.

Based on the features you’re looking for, I would think that Community Edition or Pro are the correct choices, as they support the features you’re looking for. Earlier in the thread, you mentioned that Community Edition doesn’t align with your technical and operational needs. Is there a reason why you can share?