Releasing Java SDK packages » History » Version 13
Brett Smith, 11/04/2025 02:11 PM
update for Sonatype Central Repository migration
| 1 | 1 | Peter Amstutz | h1. Releasing Java SDK packages |
|---|---|---|---|
| 2 | |||
| 3 | The Java SDK is distributed on the Sonatype artifact repository. Here are the steps to release a new jar file: |
||
| 4 | |||
| 5 | # Build and upload package using https://ci.arvados.org/view/All/job/build-java-sdk |
||
| 6 | 13 | Brett Smith | # Go to "Sonatype Publishing Settings":https://central.sonatype.com/publishing/deployments and log in with the appropriate credentials (gopass oss.sonatype.org/curii) |
| 7 | # Make sure you're on the "Deployments" tab. |
||
| 8 | # Find the jar that was just uploaded by Jenkins. Click the "Publish" button and wait for the process to finish. |
||
| 9 | 8 | Peter Amstutz | |
| 10 | h2. Getting the authentication token for Sonatype |
||
| 11 | |||
| 12 | 13 | Brett Smith | "Log into Sonatype":https://central.sonatype.com/usertoken and under the account menu select "User Tokens" to review and manage tokens. Our current Jenkins token is stored in gopass as @curii-systems/websites/oss.sonatype.org/jenkins@. |
| 13 | 8 | Peter Amstutz | |
| 14 | 4 | Peter Amstutz | h2. gradle.properties |
| 15 | |||
| 16 | 13 | Brett Smith | To upload to Sonatype, you need the token (see above) and a secret key. You must upload a GPG-signed package. All these parameters are set in @gradle.properties@ which we keep as a Jenkins secret. Note that the property values after the equals sign should not be quoted. I'm not certain if spaces are allowed around the equals sign, but currently it works with no extra spaces. |
| 17 | 10 | Peter Amstutz | |
| 18 | 1 | Peter Amstutz | <pre> |
| 19 | 8 | Peter Amstutz | ossrhUsername=... |
| 20 | 4 | Peter Amstutz | ossrhPassword=... |
| 21 | 9 | Peter Amstutz | signing.keyId=... |
| 22 | signing.password= |
||
| 23 | signing.secretKeyRingFile=...-secret-key.gpg |
||
| 24 | 3 | Peter Amstutz | </pre> |