[
https://issues.jenkins-ci.org/browse/JENKINS-11938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159951#comment-159951
]
Mehul Sanghvi commented on JENKINS-11938:
-----------------------------------------
This is from an email I sent out to the Jenkins mailing list
dated 2011-06-24. Unfortunately as I no longer work at the
place, I am unable to provide further information about what
version of Jenkins it was, etc. I thought it would be good
to have this captured here in case it helps out in testing
or following the code path.
------ begin email ------
I had the following three Jobs in Jenkins:
mehul-nightly
BRANCH_5_X
BRANCH_5_X-nightly
mehul-nightly was the one I was actively working on. Once I got it
configured and working the way I wanted it to work,
I did the following:
- deleted BRANCH_5_X-nightly
- renamed mehul-nightly to BRANCH_5_X-nightly
I went to bed around 1:30am having checked the log for build #258
which was a success.
This morning when the BRANCH_5_X-nightly ran at 2am, it got an
unstable status (not an issue), but I no longer see
any logs for the previous 258 builds! I looked on the Jenkins servers
and there are no log files
for any of the builds.
Does anyone have pointers on what could have gone wrong or happened ?
----------- end of email --------
> 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
