Because Cruise installs itself as a service (Windows) or daemon (Linux) by default, getting Cruise Agents to interact with your operating system's windowing environment can cause problems. Access to a windowing environment is usually required for testing UI applications or for driving browsers for web testing. Here's how you do it.
The first step is to disable the Cruise Agent service. To do this:
- Log in to your Windows machine as an Administrative user.
- Click on Start -> Control Panel -> Administrative Tools -> Services.
- Double click on 'Cruise Agent'.
- Change the Startup Type to 'Disabled'.
- Click 'Stop' to stop the service.
- Click 'OK' to finish.
The next step is to start the Cruise Agent as an application.
- Click on Start -> All Programs -> Cruise Agent -> Run Cruise Agent.
- To get the Cruise Agent to start every time you log in, copy the Run Cruise Agent shortcut to the Startup folder of your start menu.
There are many different ways to get a Linux build agent to interact with a UI. The easiest is to use a VNC service to provide a dedicated X11 server to your agent. To do this:
- Install the VNC server and fvwm packages for your distribution. (aptitude install vnc4server fvwm / yum install vnc-server fvwm)
- Sudo to the 'cruise' user (sudo su - cruise) and do the rest as that user
- Set a password for remote access to your VNC server with the command 'vncpasswd'
- Edit your VNC config to use fvwm and not twm as the window manager. (replace twm with fvwm in ~/.vnc/xstartup
- Edit '/etc/default/cruise-agent' and change the line 'VNC=N' to 'VNC=Y'
Restart your agent and it will now have access to an X11 server that you can also connect to with your favourite VNC client. The default DISPLAY that Cruise uses is :3