In case you'd be running into the same issue as me... I currently have the same kind of issue for a few months now : it happens for jobs who uses a file upload parameter.
There is a workaround for this bug though : Remove the <dfosFile>.*</dfosFile> tag from the jobs' build.xml and replace it by <cachedContent></cachedContent> I do it with sed in a separated job running after the bugging jobs ; that appears to fix the issue. 2013/1/10 <rhythmicde...@gmail.com> > I believe that I am having the same issue. > > > https://groups.google.com/forum/?fromgroups=#!topic/jenkinsci-users/7GZJaajfYvM > > Did you find any resolution? > > Steve > > > On Wednesday, January 2, 2013 3:24:56 PM UTC-5, Ryan Shoemaker wrote: >> >> Was there an issue filed for this? >> >> I'm running 1.492 and noticed the disappearing build issue in a new job I >> created today (all of our existing jobs seem to behaving normally). Builds >> of the new job do exist on disk on the Jenkins server, but they aren't >> showing in the UI. At least not for very long. They appear for a little >> bit and then disappear. When they do exist, the hover-over context menu >> only shows a few of the usual options. >> >> --Ryan >> >> On Tuesday, 23 October 2012 09:49:32 UTC-4, Andrew Melo wrote: >>> >>> Hey everyone, >>> >>> We're on 1.486, but we're still having our build records disappear, >>> did the planned fixes not make it into the release? >>> >>> Thanks, >>> Andrew >>> >>> -- >>> -- >>> Andrew Melo >>> >>
