> On Thu, Feb 23, 2012 at 5:43 PM, Vojtech Juranek <[email protected]> wrote: > >> Does the groovy plugin need anything special installed on the slaves? > > > > there are two options, groovy script and system groovy script. First one > > requires groovy installation on slaves (check global jenkins > > configuration, auto-install can be used), second doesn't, however it's > > not executed on slave, but in master JVM (it uses bundled groovy lib in > > the same way as you run groovy script via groovy console) > > I don't get it. The script console in the node screen works and runs > on the slaves. For example I can run 'println "ipconfig > /all".execute().text and I get results that are obviously coming from > the windows slave even though the jenkins server and master jvm are on > linux. Or is that remoted with some java magic?
exactly, slave agent has remote class loader which is able to load all necessary classes from master (if you are interested in technical details, see [1]). If you consider similar function/build step useful, please file a feature JIRA request for me, it shouldn't be very difficult to implement it. > I checked the auto-install option but it doesn't seem to make any > difference. Should the attempt to install be logged somewhere so I > can see if it failed? installation should be visible in the log (in log of the build which tries to install groovy before launching groovy commands). Could you provide some details or log a JIRA for it if you think it's a bug? Thanks [1] https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/util/RemotingDiagnostics.java#L115
