Release workflow with Maven and Nexus

Question

1. Is there any way to setup Bamboo to make release versions follow the Maven version?  Something along the lines of ${maven.version}-b${buildNumber}.

2. The artifacts need to be published to Nexus.  Is the expected workflow here that the build plan publishes the artifacts or that a Deployment publishes the artifacts?

3. I haven't found any Nexus related plugins which is strange to me since it's so commonly used.  Is the only option for tying promotions in Bamboo to promotions in Nexus with some sort of bash script to call their API?

Chandler Zhang · Answer

he problem is that Bamboo is using a cached repository, so even when using the maven-nexus-plugin, the plugin cannot push the commits with the release tag back to the repository (in my case Bitbucket Server).

Do you mean maven-release-plugin? Could you please provide some logs of your build? We use maven-release-plugin and don't have the problem

Adam Pryce · Answer

The problem is that Bamboo is using a cached repository, so even when using the maven-nexus-plugin, the plugin cannot push the commits with the release tag back to the repository (in my case Bitbucket Server).

LarsM · Answer

You can use the maven-nexus-plugin and run it in the release-plugin - see http://www.baeldung.com/maven-release-nexus

And then use a Maven2/3 Task to execute it.