-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
None
-
Jenkins LTS 1.580.2
Windows 7
After the Jenkins Server was running out of diskspace, the history of the old builds is missing for all active Jobs. The History is still physically available. Just the list of all builds disappeared from the Jenkins Webpage. Jobs which were started after the missing diskspace problem are listed, only jobs before that problem are affected.
[JENKINS-26599] Missing build history after full disk
Florian Reiser
added a comment - Unfortunately it is not simple to provide you with the jenkins.log, because it is entangled in the tomcat.log. I can try to separate the right time region, but so far I saw nothing of importance.
But I found out something different, that seems to be related with this problem. Under "Jenkins" -> "Manage Jenkins" I receive the following message:
Some projects have builds whose timestamps are inconsistent. These will confuse Jenkins when it tries to look up build records. Correct those problems by moving offending records to a backup folder
I don't want to move the old builds to a backup folder. I just want to correct the timestamps. Is there a possibility?
Thanks in advance.
Florian Reiser
added a comment - Unfortunately it is not simple to provide you with the jenkins.log, because it is entangled in the tomcat.log. I can try to separate the right time region, but so far I saw nothing of importance.
But I found out something different, that seems to be related with this problem. Under "Jenkins" -> "Manage Jenkins" I receive the following message:
Some projects have builds whose timestamps are inconsistent. These will confuse Jenkins when it tries to look up build records. Correct those problems by moving offending records to a backup folder
I don't want to move the old builds to a backup folder. I just want to correct the timestamps. Is there a possibility?
Thanks in advance. Florian Reiser
added a comment - Unfortunately it is not possible to attache the jenkins.log here. Several of the information in the logs are company restricted. There are to many log entries, hence it is not possible to cut all restricted information out.
Florian Reiser
added a comment - Unfortunately it is not possible to attache the jenkins.log here. Several of the information in the logs are company restricted. There are to many log entries, hence it is not possible to cut all restricted information out. Florian Reiser
added a comment - The problem resolves it by itself after a complete restart of the Jenkins server. I couldn't try this before, because the system is in productive use.
The message about inconsistent timestamps is a little bit confusing if a simple restart is sufficient. Maybe it is possible to change this message.
Florian Reiser
added a comment - The problem resolves it by itself after a complete restart of the Jenkins server. I couldn't try this before, because the system is in productive use.
The message about inconsistent timestamps is a little bit confusing if a simple restart is sufficient. Maybe it is possible to change this message. 
This report needs much more information. Anything in Old Data Monitor? The jenkins.log?
https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue