|
|
|
Issue Type:
|
Bug
|
Assignee:
|
stephenconnolly
|
Components:
|
credentials, subversion-plugin |
Created:
|
14/Oct/14 4:36 PM
|
Description:
|
After updating Jenkins from 1.551 to 1.565.2, our jobs fail, more often than not, with the SVN exception
"E200015: No credential to try. Authentication failed"
I know this has occurred before, but in our case, it is neither externals-only nor are there any parameters involved. Also, it is not restricted the first one. It doesn't happen every time, but about every second time.
According to the SVN server's connection logs, Jenkins actually tries to connect to the SVN server without giving any credentials in those cases.
|
Environment:
|
Windows 7
Jenkins 1.565.2
Subversion Plugin 2.4.3
|
Project:
|
Jenkins
|
Labels:
|
credentials
Subversion
|
Priority:
|
Major
|
Reporter:
|
Jennifer Hofmeister
|
|
|
|
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
jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/d/optout.