cloudogu / command-bus Goto Github PK

The Tool-Name for JDK-8 should be changed from JDK8 to OpenJDK-8 as that is the default value for our Jenkins and it can cause problems if the tool name is wrong.

0.2.1 is our first version on maven central. 🎉

The next step should be to deploy to maven central automatically using Jenkins.

Here's a first pragmatic approach:

• Any commit on the master branch will be deployed into sonatype release repo (from there it will be automatically synced to maven central)
• That is, (for now) the version has to be set manually, e.g. with mvn versions:set -DnewVersion=1.2.3. Then commit, tag and push. Don't forget to set the next SNAPSHOT version manually on develop branch.
• Push to master will trigger the deployment (realized in Jenkinsfile in deploystage)
• In order to deploy to maven central, Jenkins needs to provide the following
  • gpg binary (e.g. via Docker. The official maven image contains it for example. Tested on 3.5.0-jdk-8)
  • Import gpg key from jenkins credentials: gpg --import $ascFile
    Or: Pass Keyrings from credentials to maven: -Dgpg.publicKeyring=$publicKeyring -Dgpg.secretKeyring=$privateKeyring
  • A secret that contains the gpg passphrase
  • A settings.xml that contains an access token generated at oss.sonatype.org for a user that is allowed to deploy to de.triology

    <server>
      <id>ossrh</id>
      <username>usertoken-username</username>
      <password>usertoken-password</password>
    </server>

• Do the deploy on jenkins using maven:
  mvn deploy -P release -Dgpg.passphrase=$passPhrase -s $settingsXml

Further improvements could be to automate further (setting versions, tagging, gitflow).
The difficult part about that one is that pushing version changes to Git triggers another build.