Arvados

h1. Releasing Java SDK packages

The Java SDK is distributed on the Sonatype artifact repository.  Here are the steps to release a new jar file:

reference: https://central.sonatype.org/publish/release/

# Build and upload package using https://ci.arvados.org/view/All/job/build-java-sdk

# Go to https://oss.sonatype.org and log in with the appropriate credentials (gopass oss.sonatype.org/curii)

# Under "Build Promotion" on the left sidebar, click on "Staging Repostories"

# Find "orgarvados-XXXX" and click on it

# In the toolstrip, click on "Close" -- this locks the repository against further changes and runs validation checks

# The validation checks take a few minutes.  You can monitor it on the "Activity" tab

# Once the validations have passed, you'll be able to hit the "Release" button

# This moves the packages to the release repository and drops (deletes) the staging repository

# Reportedly there is lag of a few minutes on when a released package becomes visible / searchable

h2. Getting the authentication token for Sonatype

# Go to https://oss.sonatype.org and log in with the appropriate credentials (gopass oss.sonatype.org/curii)

# Click on "Curii" in the upper right and go to "Profile"

# There will be a drop down menu that says "Summary", click on it and select "User Token"

# There will be a button "Access User Token", click on it and it will give a random string for username and password 

# Paste those into @gradle.properties@

# Update the credentials on Jenkins

h2. gradle.properties

To upload to Sonatype, you need the token (see above) and a secret key.  On Jenkins, there is a package signing key which you need to also specify.  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.

<pre>

ossrhUsername=...

ossrhPassword=...

signing.keyId=... 

signing.password= 

signing.secretKeyRingFile=...-secret-key.gpg 

</pre>