Hi,
I have difficulties to set the DISPLAY environment variable on my
ssh-controlled Linux build slave. Selenium wants the browser binary, so
writing a shell script like
DISPLAY=:1 /usr/bin/firefox $@
does not work well.
When I add export DISPLAY in .bashrc or .profile on the slave, the ssh
slave launcher does not pick it up. Rather, it seems to have its very own,
reduced set of environment variables. Is this a feature of the ssh slave
implementation?
What is the reason why the environment variables on the slave configuration
page are not exported to the ssh slave environment? Is it because that
wouldn't work with sshd anyway?
I am patching the selenium plugin to use a tunnel right now (which works
already), I might as well try to do something about the DISPLAY. The main
problem right now is, how should I set the env variable (with
connection.exec("set")?) and how can I access the environment variables
defined on the slave configuration page from the ssh-slaves plugin?
Has anybody considered this before and give me some advice what might work
and what won't?
Best regards,
Dietrich
