Community
Participate
Working Groups
I think it is regression or it was not fixed properly. I see very same results as described here: https://issues.jenkins-ci.org/browse/JENKINS-2909 with Hudson 3.3.3 and subversion plugin 2.3.11 Maybe the only difference is that it happens only for cases where there is more than one possible account, but all of them are wrong. It results in dozens "authentication failed" logs per second on svn server for every such user: user USERA: authentication failure for "/xxx": Password Mismatch user USERB: authentication failure for "/xxx": Password Mismatch user USERA: authentication failure for "/xxx": Password Mismatch user USERB: authentication failure for "/xxx": Password Mismatch ...etc.
Ok. there were multiple subversion.credentials entries in job and in globals Hudson scope, all of them - invalid. However event entering project settings (which checks svn connections and shows current status) caused endless round robin try of every such credential andthere was no status on settings page at all (neither ok nor error). Even changing credential in such project and providing correct password did not stop already started background endless loop. Current workaround - delete subversion.credentials in job scope and globals and hard restart of jetty running hudson. Only this helped.
