Closing as I think this is resolved now. odlparent has a way to release separately from autorelease which was the intent of this issue.

This is complete with the merge of this patch
https://git.opendaylight.org/gerrit/58760

The following global-jjb patch adds a working job that can release.

https://gerrit.linuxfoundation.org/infra/5126

Once it's merged we can add the bits to releng/builder to put the job into production.

(In reply to Michael Vorburger from comment #9)
> > need to push a staged repo to Nexus
>
> doesn't the org.sonatype.plugins:nexus-staging-maven-plugin do what you are
> after? I use that e.g. in my https://github.com/vorburger/MariaDB4j to
> deploy a personal project to Maven central, and it works great - bumps the
> versions, pushes to a staging...

That's what we're currently using for however Sonatype is currently hasn't fixed their issue with SNI in the plugin unfortunately and they don't seem to have made any progress since I reported it months ago. See [0] for details. We're currently using a workaround which is not great to allow autorelease to push however it's not a good workaround.

Moving forward we are going to be using Curl to upload things directly to Nexus as it will get around the SNI issue and allows us to also support non Java / Maven projects as we want to provide a solution that can worth for any type of project. I have a bash script that is mostly working now. I hope to have it fully ready by Monday.

[0] https://jira.linuxfoundation.org/browse/RELENG-21

> need to push a staged repo to Nexus

doesn't the org.sonatype.plugins:nexus-staging-maven-plugin do what you are after? I use that e.g. in my https://github.com/vorburger/MariaDB4j to deploy a personal project to Maven central, and it works great - bumps the versions, pushes to a staging...