Xvnc Plugin

Skip to end of metadata
Go to start of metadata

Plugin Information

Plugin ID xvnc Changes In Latest Release
Since Latest Release
Latest Release
Latest Release Date
Required Core
Dependencies
1.17
Mar 16, 2014
1.444
Source Code
Issue Tracking
Maintainer(s)
GitHub
Open Issues
Levon Saldamli (id: levsa)
Usage Installations 2013-Apr 1692
2013-May 1661
2013-Jun 1661
2013-Jul 1765
2013-Aug 1757
2013-Sep 1795
2013-Oct 1821
2013-Nov 1803
2013-Dec 1772
2014-Jan 1853
2014-Feb 1926
2014-Mar 2046

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 and ending with :99.
(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 ten 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 Jenkins fails. This blog post describes how.

If you are running Windows you probably do not want this plugin. This blog post offers an alternative suggestion.

Version History

Version 1.17 (Mar 16 2014)

  • issue #22105 Client is not authorized to connect to Server.
    This will reintroduce the problem with spaces in job names. To avoid that bug:
    • avoid using spaces in job names, or
    • fix the vncserver script: add qoutes around the xauthority filename when xauth is called, or
    • turn off per job xauthority file generation.

Version 1.16 (Mar 5 2014)

Version 1.14 (Apr 10 2013)

  • issue #17280 Display number out of bounds, no way to reset
  • issue #17550 Xvnc plugin tries to use already allocated displays

Version 1.13 (Apr 9 2013)

  • Automatic clearing of blacklist when run out of available ports

Version 1.12 (Apr 4 2013)

  • Changed the configurable base display number to a configurable range of display numbers.
  • Randomly retry ten times to find a working display number before giving up.
  • issue #16879 More robust display detection needed - builds fail when many builds require Xvnc

Version 1.11 (Jan 14 2012)

  • issue #8670 Bind vncserver to localhost for enhanced security.

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

Version 1.4

  • Updated to work with the latest Hudson patch

Labels

Edit
plugin-buildwrapper plugin-buildwrapper Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Add Comment