Hello, I was wondering if there are any recommendations or best practices on a typical setup for running jobs on a Linux slave, when said job contains some unit tests that require access to the GUI?
I'd be in favor or keeping these to a minimum, but at the moment we're trying to move our slaves away from Windows nodes (started using the JNLP launcher) to Linux nodes (started over SSH) because of too many issues using the Windows slaves (rather large workspaces with file locking issues when attempting to delete them, etc...). This is working fine so far, except that all our GUI tests are failing as currently our linux slaves are headless. There's a graphical environment installed, but when the SSH slave plugin initiates the connection it opens a normal SSH connection without exporting the display and it doesn't have control of the node's display. So, what would be the proper way to run GUI tests on Linux nodes started using the SSH Slaves Plugin? Thanks in advance for your suggestions. -- Laurent Malvert -- You received this message because you are subscribed to the Google Groups "Jenkins Users" 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/d/optout.
