|
||||||||
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 |
[JIRA] (JENKINS-13835) E175002 in org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request
- [JIRA] (JENKINS-13835) E175002 in org.tmate... k...@kohsuke.org (JIRA)
- [JIRA] (JENKINS-13835) E175002 in org.... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-13835) E175002 in org.... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-13835) E175002 in org.... k...@kohsuke.org (JIRA)
- [JIRA] (JENKINS-13835) E175002 in org.... ariste...@java.net (JIRA)
- [JIRA] (JENKINS-13835) E175002 in org.... valerie.wag...@sri.com (JIRA)
- [JIRA] (JENKINS-13835) E175002 in org.... valerie.wag...@sri.com (JIRA)
- [JIRA] (JENKINS-13835) E175002 in org.... valerie.wag...@sri.com (JIRA)
- [JIRA] (JENKINS-13835) E175002 in org.... arvid.arnt...@gmail.com (JIRA)
I found the cause of one of the enormous confusions with this plugin for me. If you have a matrix build, then:
you will find the old cached credentials. In all my testing trying to solve the original problems with svnkit upgrade, I changed the user and reset the password.
It would have been great if somewhere jenkins would have reported which user it was trying to use. Also, deleting the job from the client, doesn't clear the credentials buried against every axis on the server. Why are they on every axis?