Details
-
Type:
Task
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Not A Defect
-
Component/s: m2release-plugin, subversion-plugin
-
Labels:None
-
Similar Issues:
Description
I am trying to configure Maven Release plugin in Jenkins job. I am getting authentication exception. For invoking maven release plugin do we need to have svn client from where we are invoking the release? The requirement is as follows:
My requirement is to configure maven release plugin as follows:
1. My current version is at 1.0.0-SNAPSHOT and once testing is done and ready for movement to production the maven release plugin will be invoked from Jenkins job to move the code from branch to trunk.
2. The configuration has to check out the source from branch, update all the POMs to version 1.0.0, tag the source code and check in the code at trunk location. The tags folder will contain the tagged version at 1.0.0 (as best practice we need to change the version from 1.0.0-SNAPSHOT to 1.0.0 once the product is ready for production, right? or while moving to UAT itself it should be done?).
3. Also, the next snapshot version will be updated to 1.0.1-SNAPSHOT(which is configurable in release plugin) and checked in at branch level for the next development.
I am able to configure this, but somehow it is not working. I am getting authentication exception.
svn: Authentication required for '<https://server-mydomain.com:443>'.
Attachments
Activity
Reassigning to m2release plugin
Peter Hayes
added a comment - Reassigning to m2release plugin Hi, Please help in configuring the plugin properly. I wanted to know details like:
1. any certificate needs to be installed on jenkins/client from where the release is performed?
2. whether the configuration given in the POM files is correct for maven release plugin?
3. any other configuration that I have missed.
Vijay D
added a comment - Hi, Please help in configuring the plugin properly. I wanted to know details like:
1. any certificate needs to be installed on jenkins/client from where the release is performed?
2. whether the configuration given in the POM files is correct for maven release plugin?
3. any other configuration that I have missed. 
Please see the faq at https://wiki.jenkins-ci.org/display/JENKINS/M2+Release+Plugin
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 on how to configure this please use the Jenkins users mailing list