On the job configuration page, enable the "Maven release build" under the Build Environment heading and add whatever release goals and options your require.
Follow the "Perform Maven Release" link
Nexus staging will create a new Stage for each unique IP Address, deploy users and HTTP User agent.
For a particular Jenkins slave the first two will be the same for all builds - so you need to configure Maven to use a unique HTTP User-Agent for the deploy.
To do this make sure your maven settings contains something like the following where the id matches the id for the release repository in the deployment section of your project:
If your build fails with the following:
Then this is a maven bug not a Jenkins plug-in bug.
The solution is to upgrade to version 2.0-beta-8 or later of the maven-release-plugin in your project.
Some users with CVS (cvs+ssh) have reported that a release just hangs while accessing the ssh server (JENKINS-4783). The solution is to use the native CVS client and append "-Dmaven.scm.provider.cvs.implementation=cvs_native" to the release arguments.
The use of this plugin requires that Maven can tag your code. You may need to use cvs/svn etc from the CI account on the server that is performing the release so the native tools used by maven have the required authentication information. (this is outside of Jenkins SCM authentication)
For Help and support please use the Jenkins Users mailing list.
In no order:
Skip to end of metadata Go to start of metadata