On Fri, Dec 18, 2009 at 9:49 AM, Tim Ellison <t.p.elli...@gmail.com> wrote: > On 17/Dec/2009 21:03, Niklas Gustavsson wrote: >> we now got a Windows server ready for installing a Hudson slave. As >> there is a need to run GUI tests on the slave, the recommended way of >> running Hudson is to use JNLP. > > Excuse my ignorance, but why does the method of invoking the Hudson > slave affect what type of code that slave can run? The GUI tests are > run in a separate JVM forked from a script launched by Hudson...
The other way of running the Hudson slave is as a Windows service, and as far as I know, a service does not have access to GUI. You can find more details on the options here: http://wiki.hudson-ci.org/display/HUDSON/Distributed+builds#Distributedbuilds-HavemasterlaunchslaveagentonWindows > Solaris - <shrug/>. It may be simpler to put ssh on the windows side > and have everything work the same way. That is certainly also an option. There is a write up on the experience the Sontype guys had with Hudson/Windows/SSH here: http://www.sonatype.com/people/2009/02/the-hudson-build-farm-experience-volume-ii/ /niklas
