It ran twice on a Saturday while that's not possible according to one of the crons:

H/30 7-22 * * 1-5

The server time is correct.


This is the whole System Information page: https://gist.github.com/frvge/28884e6755a2610ec2cb (removed a few IPs).

We upgraded to the version with the new build layout so I'd prefer not to downgrade. With > 500 jobs I don't want to take chances that something goes wrong. I can do it, but only as a last resort.

Jenkins is running in a screen session. Maybe that also has something to do with it?

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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to