[
https://issues.jenkins-ci.org/browse/JENKINS-11938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159950#comment-159950
]
Dorin Marinca edited comment on JENKINS-11938 at 3/7/12 4:51 PM:
-----------------------------------------------------------------
+1 Same issue on winxp_sp3 jenkins 1.452 (but seen several times in older
versions). using setenv 1.1 and not using envinject.
The builds don't reappear on "Reload Configuration from Disk". Could somebody
suggest how could I force this reload differently?
It's critical in my context as we users download often latest successful
artifacts from jenkins.
It seems that the jobs where this issue are parametrized with load file.
FYI (I don't know if it's related but) in jenkins.err.log file I have a lots of
exceptions like this on various upload*.tmp files:
---- Debugging information ----
message : Could not call
org.apache.commons.fileupload.disk.DiskFileItem.readObject()
cause-exception : java.io.FileNotFoundException
cause-message :
C:\DOCUME~1\dmarinca\LOCALS~1\Temp\upload__4065e0d0_1351ff4c1c6__8000_00000013.tmp
(The system cannot find the file specified)
class : hudson.model.FreeStyleBuild
required-type : org.apache.commons.fileupload.disk.DiskFileItem
path :
/build/actions/hudson.model.ParametersAction/parameters/hudson.model.FileParameterValue/file/org.apache.commons.fileupload.disk.DiskFileItem
line number : 19
-------------------------------
could be interpreted this as:
parametrized builds loose somehow some of their hidden data files (e.g.
uploaded files used during builds) and thus they cannot be shown by jenkins in
history?
was (Author: dim):
+1 Same issue on winxp_sp3 jenkins 1.452 (but seen several times in older
versions). using setenv 1.1 and not using envinject.
The builds doesn't reappear on "Reload Configuration from Disk".
> 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
