The only difference I see between what is working on my environment is the servers used to copy from and to are different.
One will come from where Jenkins has checked out from, the other will come from your pom. Although "mydomain" and 192.168.30.48 are very possibly the same machine you could try changing Jenkins/pom.xml so they are both identical. (I recommend using the fully qualified domain name) Other than that - I am not an expert on WebDAV and don't know if not hading access at the root of the repo would/should/could block that user being able to create the tag. /James From: [email protected] [mailto:[email protected]] On Behalf Of Angelo Scaldaferri Sent: 30 April 2013 13:12 To: [email protected] Subject: Re: [M2Release] MAVEN RELEASE - SVN 403 Forbidden I understand what you mean, but in my configuration I've already specified the user and password that have to be passed to the maven release plugin, in fact these are visible in the log file, as you can see: [LOG] Executing Maven: -B -f /opt/...thepath.../pom.xml -DdevelopmentVersion=1.2.31-SNAPSHOT -DreleaseVersion=1.2.30 -Dusername=myusername -Dpassword=********* -DscmCommentPrefix=[maven-release-plugin] -Dtag=1.2.30 -Dresume=false release:prepare release:perform [/LOG] I suspect that Jenkins try to reach the root of the svn folder in the release:prepare phase with the user that I've specified, but this user can see only the leaf of the project and not the root of the company's svn... svn --username myusername --password '*****' --no-auth-cache --non-interactive copy --file /tmp/maven-scm-1426693027.commit --revision 26982 http://mydomain/svn/svnroot/myproject/trunk http://192.168.30.48/svn/svnroot/myproject/tag/1.2.30 >> in response to PROPFIND request for '[root_dir_svn]' Regards Angelo Il giorno lunedì 29 aprile 2013 22:56:56 UTC+2, teilo ha scritto: The release process will use the authentication available to the subversion command line client when run as the user that Jenkins runs as on the slave. If you have not told the release plugin otherwise it won't pass a user to the svn client either, so if Jenkins is running as root it will try and create the tag as the root user. It sounds like you need to use a user other than root and if you don't want to have to specify a username/password eachtime then you can add -Dusername=myuser to the real ease goals and put the password for this used in the subversion credential cache (this is not the Jenkins svn credential store) -- 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 [email protected]<mailto:[email protected]>. 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
