-
Bug
-
Resolution: Unresolved
-
Minor
-
None
I short, it seems like the latest version of Xvnc is outputting a .log file by default, and the Jenkins Xvnc plug-in is only looking for .pid files when cleaning up after the job has run. It seems like all that needs to be done is look for both .pid and .log files in the cleanup step.
Example log file:
Started by user Foo ... Starting xvnc [Job Name] $ vncserver :66 -geometry 1280x1024 -depth 24 sh: 1: Syntax error: "(" unexpected sh: 1: Syntax error: "(" unexpected New '36e5ed42de5a:66 (jenkins)' desktop is 36e5ed42de5a:66 Starting applications specified in /home/jenkins/.vnc/xstartup Log file is /home/jenkins/.vnc/36e5ed42de5a:66.log ... Terminating xvnc. $ vncserver -kill :66 Can't find file /home/jenkins/.vnc/36e5ed42de5a:66.pid You'll have to kill the Xvnc4 process manually Finished: SUCCESS
[JENKINS-30602] Xvnc plugin only looks for .pid files not .log files
Hays Clark
added a comment - Very strange... my job was throwing the error above until I unchecked the "Create a dedicated Xauthority file per build?" checkbox, which fixed by Jenkins job; however, the "Can't find file /home/jenkins/.vnc/[...].pid" error no longer shows up.
Starting applications specified in /home/jenkins/.vnc/xstartup Log file is /home/jenkins/.vnc/f49349b862b0:25.log ... 84 of 84 tests passed. All tests passed! Terminating xvnc. $ vncserver -kill :25 Killing Xvnc4 process ID 165 Finished: SUCCESS
Hays Clark
added a comment - Very strange... my job was throwing the error above until I unchecked the "Create a dedicated Xauthority file per build?" checkbox, which fixed by Jenkins job; however, the "Can't find file /home/jenkins/.vnc/ [...] .pid" error no longer shows up.
Starting applications specified in /home/jenkins/.vnc/xstartup
Log file is /home/jenkins/.vnc/f49349b862b0:25.log
...
84 of 84 tests passed.
All tests passed!
Terminating xvnc.
$ vncserver -kill :25
Killing Xvnc4 process ID 165
Finished: SUCCESS
Hrm.... after looking at the plug-in code (line 229 of Xvnc.java), I'm wondering if the actual bug is in Xvnc server when 'kill' is called on the pid.