由于密码更改,我们在 Jenkins 中的一项工作失败了,它的颠覆轮询超过 24 小时。当这种情况发生时,并不是立即显而易见的,除非您注意到作业没有运行并实际检查日志,构建不会失败,因为它从未启动。
有没有人找到解决方案来通知 Jenkins 管理员任何轮询失败?我当前的想法是安排相同或定期启动的第二个作业,以确保登录有效。
http://jenkins.mycompany.com/view/Builds/job/Trunk/scmPollLog/ 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)
...
詹金斯现在不支持这一点,因为轮询发生在工作环境之外 https://issues.jenkins-ci.org/browse/JENKINS-11760.
一些想法:
首选 投票必须消亡 http://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/如果您从SVN提交钩子 https://wiki.jenkins-ci.org/display/JENKINS/Subversion+Plugin,我相信密码失败将发生在 svn update 时,因此在工作期间。您将会收到通知。您还将受益于摆脱轮询。
fix JENKINS-11760 https://issues.jenkins-ci.org/browse/JENKINS-11760 ;)
本文内容由网友自发贡献,版权归原作者所有,本站不承担相应法律责任。如您发现有涉嫌抄袭侵权的内容,请联系:hwhale#tublm.com(使用前将#替换为@)