|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
I'm marking this bug as closed as a duplicate of
JENKINS-15587.Accessing the build via URL does trigger the lazy loading (in fact there's no way to access any build without trigering a loading). Then later through other code path you manage to have the build in question loaded.
So the only plausible explanation that I have is that one is using symlinks, and the other was using build ID to load. On symlink-enabled Windows, the former would hit
JENKINS-15587, while the latter doesn't.