Update:
We just did maintenance on our gitlab server, including a start/stop of the program, and suddenly all the polling / triggers started working again. This meant a big big big queue. (which failed because we couldn't checkout the code of course).

The interesting part is that a timed job, configured like

58 23 * * *

also ran again automatically. Its running time is also not consistent with that schedule:

Failed > Console Output#1​6 Apr 1, 2015 6:21 PM
Failed > Console Output#1​5 Apr 1, 2015 6:05 PM
Failed > Console Output#1​4 Apr 1, 2015 6:04 PM
Success > Console Output#1​3 Apr 1, 2015 7:38 AM
Success > Console Output#1​2 Mar 30, 2015 10:24 PM
Success > Console Output#1​1 Mar 29, 2015 11:22 AM
Success > Console Output#1​0 Mar 27, 2015 9:43 PM
Success > Console Output#9 Mar 26, 2015 11:18 AM
Success > Console Output#8 Mar 25, 2015 4:22 AM
Success > Console Output#7 Mar 23, 2015 7:16 PM
Success > Console Output#6 Mar 22, 2015 10:23 AM
Success > Console Output#5 Mar 21, 2015 1:57 AM
Success > Console Output#4 Mar 20, 2015 12:59 PM
Success > Console Output#3 Mar 19, 2015 2:40 AM
Success > Console Output#2 Mar 17, 2015 8:45 PM
Success > Console Output#1 Mar 16, 2015 6:05 PM
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to