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].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to