This plugin lets you run an Xvnc session during a build. This is handy if your build includes UI testing that needs a display available.
Each build using the plugin gets its own display allocated from a free list, by default starting with :10.
(The $DISPLAY environment variable is set for the build by the plugin.)
Thus you can freely run builds on multiple executors without fear of interference.
If there is some problem starting a display server with a given number, that number will be blacklisted
for the remainder of the Hudson session and the plugin will try a couple more times before giving up.
This is commonly due to stale locks that did not get cleaned up properly.
There is also an option to clean up locks when starting the first Xvnc-enabled build in a given session.
Note: you must have started the vncserver at least one time before you use it with hudson. This is to create a password. Otherwise hudson fails.
Version 1.10 (Jul 19 2010)
- issue #3285 Option to clean up stale locks & processes.
- issue #3680 Do not run vncserver -kill in workspace directory.
Version 1.9 (Jun 21 2010)
- Added a mechanism to exclude Xvnc execution on specific nodes
- Added an option to skip Xvnc execution on all Windows machines
Version 1.8 (Jan 9 2010)
- Ensure screenshot is taken when selected
- Update code for more recent Hudson
Version 1.7 (Apr 15 2009)
- Retry several times before giving up on attempt to get a display, blacklisting displays each time.
Version 1.6 (Apr 14 2009)
- If the user forgot to put :$DISPLAY_NUMBER in the command line, issue a warning (report)
- Better help.
- Updated to new form validation style.
Version 1.5 (August 11, 2008)
- Can be configured to take a screenshot of the X session upon build completion. These screenshots are treated as build artifacts. This functionality requires Imagemagick
- Updated to work with the latest Hudson patch