New question #190039 on Sikuli: https://answers.launchpad.net/sikuli/+question/190039
Hi I am running Sikuli with a Jruby wrapper on a Windows VMWare VM. I can run the script fine form the command line manually. When I try and start the script from a CI server such as TeamCity or Jenkins (I have tried both, just a buildAgent for the former) the script hangs when it tries to find the first image. The engine is reported to have initialised OK. I have seen another question that is quite similar: https://answers.launchpad.net/sikuli/+question/153455 I was wondering if someone could explain why there is a dependency on running on a physical machine when executing Sikuli from a parent CI process? Is there any way I can make logging more verbose in order to troubleshoot a bit further? I have managed to spawn the script using the schtasks /run but this seems to return asycnhronously and terminate the script midflight. Running Sikuli on a remote Windows build agent is a killer feature for the Agile development community IMHO - it would be good to understand the technical barriers preventing this from happening. Many thanks Ben -- You received this question notification because you are a member of Sikuli Drivers, which is an answer contact for Sikuli. _______________________________________________ Mailing list: https://launchpad.net/~sikuli-driver Post to : [email protected] Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
