[JIRA] [core] (JENKINS-15156) Builds disappear from build history after completion

[dan...@beckweb.net (JIRA)]

Daniel Beck commented on JENKINS-15156 Builds disappear from build history after completion Christian: I also notice the "Some projects have builds whose timestamps are inconsistent." message doesn't re-check when the job and build history is re-read from disk or when jobs are pruned due to being old. It's an independent deliberately slow process only loading one build per 10 seconds to not be too expensive in terms of disk IO. The cases that look the most interesting to me are builds that are :STOLEN (e.g. two date-directory's build.xml files have the same <number>) Detecting two builds with same number is covered by the OutOfOrderBuildMonitor (JENKINS-22631) in 1.561+ and 1.554.1+. I had the same problem a few times over the last 8 months or so. It is definitely a different issue from the one reported here, as no two builds with the same number will be loaded by Jenkins – so the 'Reload from disk' cannot help here. I suggest you open a new issue and link it to this one.

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.