|
||||||||
|
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 figured out and fixed the issue. What I didn't realize before was that Jenkins does not use the JRE 1.7 I installed on the machine, it uses its own copy (at least by default) which is located under C:\Program Files (x86)\Jenkins\jre and that was JRE 1.6. The function required for converting a symbolic link to real folder name was introduced in JRE 1.7 and the Jenkins code skips the call to this function in hudson.Util.resolveSymlinkToFile if the function is not defined, hence the issue.
To fix this, I simply upgraded the Jenkins JRE to the latest 1.7 update.
It looks like the latest Jenkins installer (1.516) contains JRE 1.7.21 but that does not help existing installations where the only updated file is jenkins.war. Maybe add a note to the change log every time you ship a new JRE version to let people know they should do the same?