It's often not so clear why an integration test fails, and it's convenient to see it first hand. When debugging a build or deployment, the browser from the SSH session can be forwarded to your local machine, so that you have a visual on the issue. Additionally, if you start a webserver inside the SSH session, that can be forwarded to your local machine as well, and it can be accessed from your own browser.
To continue, make sure you've configured SSH access on your Semaphore account.
We will explore 3 possible approaches.
Suitable for when you want to access content, served inside the SSH session (Apache2, php -s, rails server, etc.). This approach is the fastest. However, if you want to use the exact same browser, which is used during a Semaphore run, the other options should be explored, which forward the complete browser.
Once the SSH session has been started, expand the generated command with -L 7654:localhost:80, like so:
ssh -L 7654:localhost:80 -o StrictHostKeychecking=no -p 44982 runner@138.201.32.20
This utilizes SSH's local port forwarding.
In the example above, 7654 is the port on your local machine, which will be tunneled to localhost:80 inside the running SSH session. If the Apache2 server is running inside the SSH session on port 80, when you visit http://localhost:7654 on your local machine, you should see the default Apache2 homepage.
Of course, you can use any other port, on which your webserver is running inside the SSH session.
Note: the tunnel will remain active, as long as your local machine is connected to the SSH session, with the modified command.
This approach forwards the complete virtual screen from Semaphore's SSH session to your local machine. Handy when you want your debugging to entirely happen inside the Semaphore environment, using one of the shipped browsers.
Like in the previous section, we'll use an SSH tunnel, but this time, we will connect to a VNC server in the SSH session, with a VNC client on your local machine.
Once the SSH session has been started, expand the generated command with -L 5900:localhost:5900, like so:
$ ssh -L 5900:localhost:5900 -o StrictHostKeychecking=no -p 44982 runner@138.201.32.20
The command will connect to the SSH session, and forward connections from your local machine's port 5900 to localhost:5900 inside the SSH session.
Once you're connected, run the following to setup and start the VNC server in the SSH session.
# install
$ sudo apt-get install -y x11vnc
# if using the Docker Light platform install Xvfb
curl -L https://gist.githubusercontent.com/rtgkurel/d4b5f41a814d2c032955ed61f231792e/raw/xvfb-dockerl.sh | sudo bash
# start
$ x11vnc -safer -localhost -nopw -forever -display $DISPLAY &
Now, on your local machine install a VNC client, and connect to the server in the SSH session.
# Ubuntu
$ wget https://www.realvnc.com/download/file/viewer.files/VNC-Viewer-6.18.625-Linux-x64.deb
$ sudo dpkg -i VNC-Viewer-6.18.625-Linux-x64.deb
$ vncviewer
For a Mac client visit https://www.realvnc.com/en/connect/download/viewer/macos/ and start VNC Viewer after the installation.
In VNC Viewer, enter localhost:5900 and connect. This connects to your local machines port 5900 which is forwarded to the VNC server inside the SSH session. A completely black window should appear in VNC Viewer. This is the virtual display in the SSH session, on which the GUI apps will be visible, after they're started.
Start one of the browsers in the SSH session, with the following commands:
# Firefox
$ firefox &
# Google Chrome
$ google-chrome --disable-gpu &
The browser window should appear inside VNC Viewer.
Note: the tunnel will remain active, as long as your local machine is connected to the SSH session, with the modified command.
The Docker Light platform doesn't come with preinstalled browsers, nor with a running Xvfb in the background. The preassumption is that these things are part of the given Docker image. Let's see how to forward a browser from a Docker image through the SSH tunnel.
Make sure that all steps are executed from above, until starting the browsers. Our job is to let the Docker image know about our running X11 server and the $DISPLAY we're using.
After running the following command inside the SSH session, Google Chrome (from the Docker container) should pop-up in your VNC Viewer.
# start a Docker image with appropriate options
docker run -it --env="DISPLAY" --volume="/tmp/.X11-unix:/tmp/.X11-unix:rw" selenium/standalone-chrome google-chrome
We're forwarding $DISPLAY and the X11 socket, so the selenium/standalone-chrome container know where to draw. You would similarly use these 2 parameters when starting up your own container, which has Xvfb configured inside it.
This approach is a bit dated and slow, but it can be helpful in some cases.
$ ssh -ACX -o StrictHostKeychecking=no -p 49204 runner@136.243.57.31
$ export DISPLAY=localhost:10
Now if you start any of the browsers in the SSH session, their window should be visible on your machine:
# Firefox
$ firefox &
# Google Chrome
$ google-chrome --disable-gpu &
If you're having difficulties forwarding a browser window, try installing the X11 apps package, and see if you can forward one of them.
$ sudo apt-get install -y x11-apps
# the command below should start a window, where two eyeballs will follow your cursor
$ x11eyes
Semaphore Docs are open source — Edit on GitHub
2009-2018 © Rendered Text. All rights reserved. Terms of Service, Privacy policy, Security.