Skip to content

Latest commit

 

History

History
42 lines (35 loc) · 2.15 KB

PUBLISHING.md

File metadata and controls

42 lines (35 loc) · 2.15 KB
Raw

Publishing artefacts to Maven Central

Dgraph owns the io.dgraph namespace on Maven Central. See JIRA ticket for details. This document contains instructions to publish dgraph4j build artefacts to Maven central.

Before Deploying

  • Get access to credentials for dgraph JIRA account on Maven Central.
  • Generate GPG credentials. Make sure you set a passphrase. You can use this guide.
  • Note down the short version of the Key ID: gpg --list-keys --keyid-format short.
  • Generate a secret key ring file if not present: gpg --export-secret-keys -o /path/to/.gnupg/secring.gpg.
  • Publish the keys to the MIT server: gpg --send-keys <key-id> (Maven Central will check for keys here).
  • Create ~/.gradle/gradle.properties and populate it with all the credentials:
signing.keyId=<…keyId…>
signing.password=<…password…>
signing.secretKeyRingFile=</path/to/.gnupg/secring.gpg>

ossrhUsername=dgraph
ossrhPassword=<…password…>

Deploying

  • Build and test the code that needs to be published.
  • Bump version by modifying the version variable in build.gradle file.
  • Update download version in README for both Maven and Gradle.
  • Update Supported Versions table in README.
  • Update dgraph4j version in grpc-netty table in README.
  • Update CHANGELOG.
  • Raise a PR for the above changes. Put the changelog in PR description and merge it.
  • Run ./gradlew uploadArchives.
  • Release the deployment by following the steps on the page Releasing the Deployment (link in references below).
  • Also cut a release tag on GitHub with the new version.

References