由于密码更改，我们在 Jenkins 的工作失败了超过 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)
...