Daniel Beck commented on Bug JENKINS-24377

Realized that the svn authentication depending on the cached of the svn password stored in the user profile. What need to be done is in the OS, try to connect to the said repository and store the encrypted password when asked. You should find a new file created under User/.subversion/svn.simple with the said realm. After that your jenkins should be able to tag without any problem.

This will override all authentication selected in Jenkins, leading to difficult to investigate problems when using multiple authentications each with only partial access to all Subversion repos used. So while a possible workaround in this case, it has severe, often undesirable side effects.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" 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/d/optout.

Reply via email to