Kohsuke Kawaguchi resolved Bug JENKINS-15799 as Fixed

I tested Jenkins 1.485 in the debugger on Ubuntu and observed the lazy loading behaviour.

Through the forced GC and accessing pages, I was able to cause Jenkins to discard records and reloads them on demand, and it worked correctly for me. I did notice that JENKINS-15587 would have caused a problem on Windows with the symlink support on. Based on the original reporter's environment and Zvi Karov's environment, which are both Windows that's capable of supporting symlinks, I'm marking this as a duplicate of JENKINS-15587.

The fix for JENKINS-15587 is scheduled for 1.507. If you continue to see this problem post 1.507, please reopen the ticket but be sure to provide the following information:

  • OS on your master
  • If Windows, whether you see symlinks in the builds directory
  • any suspicious warning/error messages in the server console output that points to a load failure of build records.
Change By: Kohsuke Kawaguchi (13/Mar/13 4:50 PM)
Status: Open Resolved
Resolution: Fixed
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Reply via email to