adding a release pipeline

[wwannemacher]

not sure if it's appropriate to make this a PR - I can't really test it until it's on master. Additionally, once it is on master, if I run into issues, I may make the changes directly on the master branch...

However, the goal here is to keep this file as slim as possible - problems will more than likely dictate changes in the jenkins-shared library.

All of that being said, I'd consider this PR to be a heads-up that I'm going to test releases of these jars on jenkins, using the attached pipeline.

[mcculls]

+1 to merge and go ahead with testing

(I assume the test release is going to go to staging on RSO and then be dropped, so it won't necessitate anything going to central)

[wwannemacher]

I am pretty sure that it will get staged, here is the snippet from the effective-pom:

    <distributionManagement>
      <repository>
        <id>sonatype-public</id>
        <url>https://repository.sonatype.org/service/local/staging/deploy/maven2</url>
      </repository>
      <snapshotRepository>
        <id>sonatype-public</id>
        <url>https://repository.sonatype.org/content/repositories/snapshots</url>
      </snapshotRepository>
    </distributionManagement>

In the settings.xml file on jenkins I do not see a server entry with sonatype-public as the ID. I also did not see anything in the jenkins-shared repo. So, I think that it will try to stage the release and fail. It's possible that git tags may be created in the process. If so, I will try to manually clean up if necessary.

[wwannemacher]

the staging plugin configuration also points to <serverId>sonatype-public</serverId>

Anyhow, I'll just have to try and see what happens.