I have a Sikuli/JRuby script I am trying to use to drive some native Windows applications for some front end acceptance tests.
The script works fine when I run it manually from the command line using the code in the workspace the build agent has cloned and manages (under C:\BuildAgent\work\....).
I have defined the same PATH variable in the build parameters section as I have running from the command line manually.
When I try to run the script from TC via the Windows build agent, the first native application launched by Sikuli never appears and the test times out waiting for it and fails.
I am running the Windows environment on a hosted VM and I remote in via RDP. It appears there is something about the way the TC build agent is running the Sikuli/JRuby script such that the native applications launched by Sikuli never appear on the screen.
Can anyone shed any light on why this might be happening?
I have looked in the agent log files and can't see anything obvious in there...