Thanks! The linked to issue appears to be exactly the problem my jenkins server is encountering.
-- *Corey O'Connor* Software Engineer, Test Automation | [email protected] | (310) 980-7111 www.ooyala.com | blog <http://www.ooyala.com/blog> | @ooyala<http://www.twitter.com/ooyala> On Tue, Oct 16, 2012 at 12:41 AM, Baptiste MATHUS <[email protected]>wrote: > > 1.485 or >= 1.485. Which precise version are you running? > The feature that I can think of is the build > lazy-loading<https://issues.jenkins-ci.org/browse/JENKINS-8754> that > was introduced in 1.485. There are some issues related to this improvement. > Some are already fixed (see comments in the previous link). > > HTH. > Cheers. > > 2012/10/15 Corey "Admiral Snackbar" O'Connor <[email protected]> > >> Hi All, >> I am having an issue where the build history is always empty in > 1.485. >> Has anybody else run into this? I've searched the jira DB and didn't find >> anything immediately. Figured I'd check here before posting a bug. Perhaps >> there is a config error on my part that is related. >> >> An unrelated issue: The timeline displayed by build history seems to >> easily kill whatever web browser I try. Is there a way to disable this >> graph short of modifying the code? We have no use for the timeline graph; >> might as well save the cycles. >> >> Cheers, >> >> -- >> *Corey O'Connor* >> Software Engineer, Test Automation | >> [email protected] | (310) 980-7111 >> www.ooyala.com | blog <http://www.ooyala.com/blog> | >> @ooyala<http://www.twitter.com/ooyala> >> > > > > -- > Baptiste <Batmat> MATHUS - http://batmat.net > Sauvez un arbre, > Mangez un castor ! >
