Guys, I found that installing Jenkins 1.403 from the archives fixed this issue. Not as nice, but it works. Now the Jenkins service can be restarted, and all the jobs show up OK. My install path was c:\Program Files\Jenkins.
Now that I can see what is happening, the problem with 1.457 (and apparently others) is this: - the jobs directory contains the folders of the created jobs, which is OK. - the "builds" directory is missing from each jobs\][; folder, only the files "nextbuildnumber" and "config.xml" are there. - inside of a normal-working Jenkins (ie: 1.403), the builds directory contains other "run" directories, which are time-stamped by name, and which contain the "log", "build.xml", and "changlog" files. - The broken Jenkins doesn't create the "builds" directory at all, but instead lets these "run" directories pile up in the root of my C: drive. So that's what I'm seeing, but would it be worthwhile for me to chase down which build broke this functionality? This seems to be a repeatable, and terrible problem.... - Tyler -- View this message in context: http://jenkins.361315.n4.nabble.com/JIRA-JENKINS-11938-Jenkins-loses-builds-when-restarted-tp4124991p4512277.html Sent from the Jenkins issues mailing list archive at Nabble.com.
