Hello Chris, I have the same problem when i try to tag a successful build. In fact i upgrade my svn plugin version from 1.39 to 2.3
Firstly i got the problem when job try to checkout/update (No credential to try. Authentication failed ). Then i set the credential and the problem was fixed. BUT, the tag problem isn't, i have always this problem (No credential to try. Authentication failed ) when i try to tag manually (tag this build link). Did you find a solution to your problem? Thanks a lot and please excuse for my bad English. chris.beech wrote > Yeah, it did - I gave up in the end and installed Win32SVN (SVN v1.7) and > now I can see what changes were made. I don't think Jenkins plays nice > with SVN v1.8 which was VisualSVN. > > I still had the tagging problem in Win32SVN until I permitted anonymous > read access, so there's something fishy still going on. The SVN Tagging > Plugin says it's using the credentials stored as part of the SVN > configuration but if that were the case I wouldn't be having any problems > - Googling around others have also had problems so I think it's a plugin > issue. > > Thanks, > > Chris -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/SVN-Tagging-Plugin-Issue-tp4693946p4701294.html Sent from the Jenkins users mailing list archive at Nabble.com. -- 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/d/optout.
