I have preferred the Xvnc plugin as a way to start the VNC server for a job, then stop it at the end of the job. That removes the need to call xvnc from your build script. The build script is started with a value already defined for DISPLAY, and programs started from that build script can use that display for their work.
If that won't work for you, then you would need to start xvnc early in your script, then execute the program under test, then stop vnc at the end of the job. Since those are the actions which the plugin already handles, I think you'll find it simpler to use the plugin. Mark Waite On Mon, May 19, 2014 at 5:57 AM, Ruchira Khandelwal <[email protected]>wrote: > Hi, > > > > In my Jenkins build I have configured xvnc.My purpose is to launch a xvnc > application when I run > jenkins build and then want some commands to be executed on the newly > opened xvnc. > > But when I run the Jenkins's build I could see that5 though the xvnc > session got created but whatever commands which I have given > in execute shell did not execute in the newly opened vnc session .Please > he;lp me and let me know what is it which I am missing. > > Please find the command which I have mentione din execute shell: > > #!/bin/tcsh > cd > /opt/soe/projects/umtsmisc/catapult/DI_TEAM/abhinav/RNC36_LR14.X_wk09.1_P > Xvnc -inetd python pyavt > setenv DISPLAY 135.245.169.11:$DISPLAY > source source_me.cshrc > vncconfig -desc > > Regards, > Ruchira > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Thanks! Mark Waite -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
