|
||||||||
|
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.
I was able to reproduce this bug on jenkins 1.556.
The problem was one of my project had a "lastSuccessfulBuild" file that was corrupted from a computer reset. (Windows Server 2008 R2)
I manually recreated the file with a valid number and saved it.
This modification got the queue and the builds going.
The exception that caught my attention was the following :
Caught exception evaluating: it.lastSuccessfulBuild.ARTIFACTS in /job/Dev_OnCommit/. Reason: java.lang.reflect.InvocationTargetException
It was this project that the file was corrupted.
I attached the faulty file even though it is probably not interesting. (only 3 bytes) You can probably reproduce the bug with this file.
FYI, we have a big jenkins setup (200+ jobs, 12+slaves (mac, pc, win, unix...))