vncserver -kill run in deleted workspace dir

Details

Description

Aleksandar Kostadinov wrote:
> We have a option in our instance to have workspace deleted after a
> build. Xvnc plug-in seems to be killing the Xvnc process after that has
> been done. And fails to start vncserver because it tries to start it in
> the workspace directory that doesn't exist any more.
> At least this is how I guess it is done
>
> So I think the vncserver command shouldn't be run in workspace but
> elsewhere.
>
> vncserver -kill :15
> FATAL: Cannot run program "vncserver" (in directory
>
"/mnt/hudson_workspace/workspace/brms-rules-matrix/jdk/java16_default/label/RHEL4_x86"):

> java.io.IOException: error=2, No such file or directory

Attachments

Activity

Code changed in hudson
User: : jglick
Path:
trunk/hudson/plugins/xvnc/src/main/java/hudson/plugins/xvnc/Xvnc.javahttp://jenkins-ci.org/commit/33051
Log:[FIXED JENKINS-3680] Do not run vncserver -kill in workspace dir.
It could already have been deleted, and the cwd for this command is probably irrelevant anyway.

SCM/JIRA link daemon
added a comment - 2010-07-19 07:08 Code changed in hudson
User: : jglick
Path:
trunk/hudson/plugins/xvnc/src/main/java/hudson/plugins/xvnc/Xvnc.java
http://jenkins-ci.org/commit/33051
Log:
[FIXED JENKINS-3680] Do not run vncserver -kill in workspace dir.
It could already have been deleted, and the cwd for this command is probably irrelevant anyway.