Hi Vijay, Try setting the username and password in the release options - or make sure you run subversion client on your slave and get it to store the subversion credentials in its cache.
/James From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of D Vijay Sent: 04 March 2014 08:36 To: jenkinsci-users@googlegroups.com Subject: Re: Maven Release Plugin throws Authentication Required error Hi, The issue is with configuring the M2Release plugin in Jenkins. I wanted some help in configuring this plugin in Jenkins like the steps that we need to follow. Vijay On Mon, Mar 3, 2014 at 9:28 PM, Baptiste Mathus <bmat...@batmat.net<mailto:bmat...@batmat.net>> wrote: Hi, Imo wrong mailing list. This is a pure maven question. Better ask it on maven users. Cheers Le 3 mars 2014 12:06, "D Vijay" <vijayd1...@gmail.com<mailto: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. 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<https://server-mydomain.com/>>'. Thank you, Vijay. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com<mailto:jenkinsci-users+unsubscr...@googlegroups.com>. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/wA80C4CgMtc/unsubscribe. To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscr...@googlegroups.com<mailto:jenkinsci-users%2bunsubscr...@googlegroups.com>. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com<mailto:jenkinsci-users+unsubscr...@googlegroups.com>. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
