Jenkins中的subversion轮询失败的电子邮件通知

时间:2013-08-16 16:10:33

标签: svn jenkins continuous-integration

由于密码更改,我们在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)
    ...

1 个答案:

答案 0 :(得分:2)

Jenkins现在不支持这一点,因为polling happens outside of a job context

一些想法: