I tried to run a job every 10 minutes indefinitely. The use case is a checker suite that constantly evaluates real customer experience. However twice now I have come back to the Remote Desktop and found the job stopped. I want this job run even if I am not logged in. A dedicated service approach that would start again on reboot. Afraid that without this iTest becomes less valuable to my organization.
Sorry for the confusion. As you mentioned, the jobs being stopped whe you logged off because you are using RDP for the connection (It is a MS property which stops the works once you out of the session). Yes, from iTest GUI you can run the job with a recurring fashion indefinitely but you need to make sure iTest GUI window should NOT be closed. When the OS gets rebooted it refreshes all the services and jobs and starts in fresh. So if we create a windows task it will always run the job as we like. The best way here is we can run iTest jobs from iTestRT e.g. `itestrt --licenseServer xxxx --itar c:/itar --job project/my_project/new_job.ffjd` So the job can run in background without any interrupt as OS scheduler will invoke this one each time even the machine gets rebooted.
You can create a windows task scheduler and execute the job using commandline. Or you can download Jenkins server and create a job there to run iTest job with commandline options. The job is being stopped when you logged off because you conneted to the PC by RDP. Instead of RDP please use VNC, the work will NOT stop after you logged off.