We had a job at Jenkins that did not perform subversion polls for more than 24 hours due to a password change. This does not immediately become apparent when this happens, unless you notice that the tasks are not being performed and are actually checking the logs, the assembly will not work, since it never started.
Has anyone found a solution to notify Jenkins administrators of any polling failures? My current idea is to schedule either the same or the second task, which runs periodically to make sure the login is valid.
http://jenkins.mycompany.com/view/Builds/job/Trunk/scmPollLog/ ?
Expected Log Example
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
Bad Log Example
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) ...
source share