|
||||||||
|
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/d/optout.
So does this mean you are using the Oracle jvm and not IBMs? I would like to rule out JENKINS-23176
We do update the class loader. This is because the Build toolkit classes needed to perform RTC related tasks like loading are not part of the Jenkins class path. The class loader we create is a URLClassLoader with the System class loader as the parent. The urls of the jars that form the toolkit have been added to it. The code that is running under that class loader does not have any dependencies on Jenkins classes so there is no need to retrieve them from the master (i.e. using the RemoteClassLoader from Jenkins).
Have you thought about installing the toolkit on each slave? We have been experimenting with the auto install of Jenkins tools and believe it can work with a zip copy of the build toolkit.