[
https://issues.jenkins-ci.org/browse/JENKINS-11938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160765#comment-160765
]
Asher Aber edited comment on JENKINS-11938 at 3/27/12 5:49 AM:
---------------------------------------------------------------
I found a workaround for this issue.
Use the following one liner in a script to create the /tmp/upload_...777.tmp
files listed in the build.xml file:
$ for file in `grep dfosFile build.xml |cut -d\> -f2|cut -d\< -f1`; do touch
$file; done
Hope this helps until a better fix is found.
Another note to clarify the issue:
The problem is that the uploaded parameter temp files that are created in /tmp
are lost or deleted for old builds.
As a result Jenkins throws an exception while reading the old build's XML
files(build.xml).
The end result is that old builds are not displayed.
The above workaround parses the XML files and creates dummy files in /tmp.
Once the /tmp files are in place Jenkins can successfully read the XML files
and show the old builds.
was (Author: aaber):
I found a workaround for this issue.
Use the following one liner is a script to create the /tmp/upload_...777.tmp
files listed in the build.xml file:
$ for file in `grep dfosFile build.xml |cut -d\> -f2|cut -d\< -f1`; do touch
$file; done
Hope this helps until a better fix is found.
Another note to clarify the issue:
The problem is that the uploaded parameter temp files that are created in /tmp
are lost or deleted for old builds.
As a result Jenkins throws an exception while reading the old build's XML
files(build.xml).
The end result is that old builds are not displayed.
The above workaround parses the XML files and creates dummy files in /tmp.
Once the /tmp files are in place Jenkins can successfully read the XML files
and show the old builds.
> Jenkins loses builds when restarted
> -----------------------------------
>
> Key: JENKINS-11938
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11938
> Project: Jenkins
> Issue Type: Bug
> Components: other, versionnumber
> Affects Versions: current
> Environment: tomcat 7.0.22
> windows server 2008 r2
> Reporter: Ben Dean
>
> Jenkins version 1.437
> If I stop the Apache Tomcat windows service, a bunch of my builds disappear
> from the history of the jobs. The missing builds are still on disk in the
> build folder, it just doesn't "find" them when making the history list.
> The jobs that lose history use the version number plugin and I had recently
> changed the version format from "4.3.${BUILDS_ALL_TIME}" to
> "4.4.${BUILDS_ALL_TIME}". The builds that disappear are all those after I
> changed this format. Also affects jobs that are downstream from those with
> version number changes.
> I could not find any Component related to the build history for a job. If
> someone knows what that should be feel free to change this. Also, sorry if
> there's not enough (or to much) information, this is the first Jenkins bug I
> have filed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
