|
||||||||
|
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.
I understand your problem. I wish we had a better solution. The problem is that code that the build toolkit uses to create/update symbolic links is in C libraries (even when using Java 7 on linux). Therefore in order for them to be loaded they need to be on the path for Java which can't be modified once Java starts. We could improve toolkit packaging to make the libraries more accessible. But you still need to specify the libraries when starting Java.
Yes, create a request on RTC for this. Maybe other people might have some better ideas. Are your slaves running on Windows or Linux?