由于密码更改，我们在詹金斯（Jenkins）从事的工作失败了，因为它的Subversion轮询超过24小时。除非您注意到作业没有运行并实际检查日志，否则这种情况不会立即显现，因为它从未启动过，因此构建不会失败。

有没有人找到解决方案以通知Jenkins管理员任何轮询失败？我当前的想法是安排要定期启动的相同或第二项工作，以确保登录有效。

http://jenkins.mycompany.com/view/Builds/job/Trunk/scmPollLog/吗？

预期日志示例

Started on Aug 16, 2013 11:55:35 AM
Received SCM poll call on  for Trunk on Aug 16, 2013 11:55:35 AM
http://svn.mycompany.com/trunk/sources is at revision 76,283
Done. Took 64 ms
No changes

日志失败的示例

Started on Aug 16, 2013 11:04:36 AM
Received SCM poll call on  for Trunk on Aug 16, 2013 11:04:36 AM
ERROR: Failed to check repository revision for http://svn.mycompany.com/trunk/sources
org.tmatesoft.svn.core.SVNCancelException: svn: E200015: OPTIONS /trunk/sources failed
    at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:375)
    ...
Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: No credential to try. Authentication failed
    at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37)
    ...