Comments on: Using Xvnc to create headless CI builds for Flex and AIR applications http://www.brianlegros.com/blog/2009/12/20/using-xvnc-to-create-headless-ci-builds-for-flex-and-air-applications/ eat, program, and be merry Wed, 21 Jul 2010 22:35:26 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Brian LeGros http://www.brianlegros.com/blog/2009/12/20/using-xvnc-to-create-headless-ci-builds-for-flex-and-air-applications/comment-page-1/#comment-27221 Brian LeGros Mon, 07 Jun 2010 01:36:31 +0000 http://www.brianlegros.com/blog/?p=656#comment-27221 @Darren - Not quite sure I can help without more details. Check out http://docs.flexunit.org/index.php?title=Continuous_Integration_Support for possibly more tips and things to try. If you still don't have any luck, email me with the contents of your xstartup file, OS details, settings in Hudson, and the contents of the shell script being run so we can pick apart what's going on. Hope this helps. @Darren – Not quite sure I can help without more details. Check out http://docs.flexunit.org/index.php?title=Continuous_Integration_Support for possibly more tips and things to try. If you still don’t have any luck, email me with the contents of your xstartup file, OS details, settings in Hudson, and the contents of the shell script being run so we can pick apart what’s going on. Hope this helps.

]]> By: Darren Jensen | Upstarthq.com http://www.brianlegros.com/blog/2009/12/20/using-xvnc-to-create-headless-ci-builds-for-flex-and-air-applications/comment-page-1/#comment-26890 Darren Jensen | Upstarthq.com Sat, 29 May 2010 11:12:32 +0000 http://www.brianlegros.com/blog/?p=656#comment-26890 Brian, I am not able to get the headless CI build to work. My setup is slightly different to yours (I am not using Tomcat), but everything else is the same. Basically, I start the build and it just hangs (here is the log). Do you have any suggestions that might help me to get this working? Started by user darren Starting xvnc [workspace] $ vncserver :99 New 'ubuntu-upstart:99 (hudson)' desktop is ubuntu-upstart:99 Starting applications specified in /var/lib/hudson/.vnc/xstartup Log file is /var/lib/hudson/.vnc/ubuntu-upstart:99.log [workspace] $ /bin/sh -xe /tmp/hudson3082626689357722831.sh + /opt/flex-sdk-3.4-testrunner/bin/adl_lin /var/development/Test_Runner.xml Xlib: extension "RANDR" missing on display ":99.0". Xlib: extension "Generic Event Extension" missing on display ":99.0". Xlib: extension "Generic Event Extension" missing on display ":99.0". Xlib: extension "Generic Event Extension" missing on display ":99.0". selected selected 1 2 2 (At this point it hangs)... Brian, I am not able to get the headless CI build to work. My setup is slightly different to yours (I am not using Tomcat), but everything else is the same. Basically, I start the build and it just hangs (here is the log). Do you have any suggestions that might help me to get this working?

Started by user darren
Starting xvnc
[workspace] $ vncserver :99

New ‘ubuntu-upstart:99 (hudson)’ desktop is ubuntu-upstart:99

Starting applications specified in /var/lib/hudson/.vnc/xstartup
Log file is /var/lib/hudson/.vnc/ubuntu-upstart:99.log

[workspace] $ /bin/sh -xe /tmp/hudson3082626689357722831.sh
+ /opt/flex-sdk-3.4-testrunner/bin/adl_lin /var/development/Test_Runner.xml
Xlib: extension “RANDR” missing on display “:99.0″.
Xlib: extension “Generic Event Extension” missing on display “:99.0″.
Xlib: extension “Generic Event Extension” missing on display “:99.0″.
Xlib: extension “Generic Event Extension” missing on display “:99.0″.
selected
selected
1
2
2

(At this point it hangs)…

]]> By: Brian LeGros http://www.brianlegros.com/blog/2009/12/20/using-xvnc-to-create-headless-ci-builds-for-flex-and-air-applications/comment-page-1/#comment-21150 Brian LeGros Tue, 12 Jan 2010 22:37:52 +0000 http://www.brianlegros.com/blog/?p=656#comment-21150 @David - That's handled by the plugin. The plugin attempts to start xvnc at the base display number (e.g. - 99) provided in the plugin configuration. Then it'll pipe everything to the display on which it was able execute Xvnc and do an export DISPLAY=:99 for the scope of the build run. At the end of the build it resets DISPLAY and calls vncserver -kill :99 for you. At least this is what I can gather while running the plugin and looking at the source to emulate the behavior in the FlexUnit4 Ant task. Hope this helps. @David – That’s handled by the plugin. The plugin attempts to start xvnc at the base display number (e.g. – 99) provided in the plugin configuration. Then it’ll pipe everything to the display on which it was able execute Xvnc and do an export DISPLAY=:99 for the scope of the build run. At the end of the build it resets DISPLAY and calls vncserver -kill :99 for you.

At least this is what I can gather while running the plugin and looking at the source to emulate the behavior in the FlexUnit4 Ant task.

Hope this helps.

]]> By: David Tucker http://www.brianlegros.com/blog/2009/12/20/using-xvnc-to-create-headless-ci-builds-for-flex-and-air-applications/comment-page-1/#comment-21140 David Tucker Tue, 12 Jan 2010 18:38:01 +0000 http://www.brianlegros.com/blog/?p=656#comment-21140 Brian, Did you have to 'export DISPLAY=:99.0' so that gflashplayer knows which display to open on? If not - is that handled by the Hudson plugin? David Tucker Brian,

Did you have to ‘export DISPLAY=:99.0′ so that gflashplayer knows which display to open on? If not – is that handled by the Hudson plugin?

David Tucker

]]>