nexusRepositoryManager update to 81.1.0-bb.0

Package Merge Request

Package Changes

https://repo1.dso.mil/big-bang/product/packages/nexus/-/blob/81.1.0-bb.0/CHANGELOG.md

Package MR

big-bang/product/packages/nexus!229 (merged)

For Issue

Closes big-bang/product/packages/nexus#171 (closed)

Upgrade Notices

🚨 UPGRADE NOTICE: Nexus Repository Manager 3.81.1-01

⚠️ Breaking Change Alert

CRITICAL: Nexus Repository Manager version 3.81.1-01 contains a breaking change that affects data persistence and will cause authentication failures after pod restarts.

---

🔄 What Changed

Sonatype modified the internal directory structure where /opt/sonatype/sonatype-work/nexus3 changed from a symlink to the persistent volume to a real directory in ephemeral storage. This causes the admin password file and other working data to be stored in ephemeral storage instead of the persistent volume.

---

✅ Required Fix

Note: The -Dkaraf.data=/nexus-data JVM parameter is already included in the package's default values, but when upgrading to 3.81.1-01, you MUST append this parameter to your override values to ensure it takes effect if your installation overrides INSTALL4J_ADD_VM_PARAMS

For example:

nexus:
 env:
   - name: INSTALL4J_ADD_VM_PARAMS
     value: "-Dcom.redhat.fips=false -Xms2703M -Xmx2703M -XX:MaxDirectMemorySize=2703M -XX:+UnlockExperimentalVMOptions -XX:+UseContainerSupport -Djava.util.prefs.userRoot=/nexus-data/javaprefs -Dkaraf.data=/nexus-data"

---

💥 Impact Without Fix

• accept-eula jobs will fail with 401 Unauthorized errors
• Admin password will be regenerated on every pod restart
• Authentication will fail after any pod restart or scaling event
• Data persistence will be broken

---

This configuration ensures all Nexus working data remains in the persistent volume as expected, with the critical -Dkaraf.data=/nexus-data parameter included in your override values.