Hi, First try do to that without using Jenkins at all. This is a pure maven configuration thing. You just seem to be missing the authentication part (see username and password parameters maybe).
When you manage to release some dummy versions of your project, then and only then try doing it from Jenkins or any other automated system. Cheers Le 6 mars 2014 15:14, "D Vijay" <vijayd1...@gmail.com> a écrit : > Dear All, > > > I need help in configuring the Maven Release plugin. I am trying to > configure the 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? PFA the errors & the configuration that I used > for this. > > 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<https://server-mydomain.com/> > >'. > > > Thank you, > > Vijay. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org >
