-
Bug
-
Resolution: Fixed
-
Major
Enabling the Xvfb plugin on matrix jobs starts a Xvfb server for the job itself and one for each configuration.
The Xvfb servers for the configurations are stoppd properly, but the Xvfb server for the job itself keeps running when the job finishes. This ends up in locked screens and a vast number of directories.
We experienced that on a master only instance as well as in master-slave mode.
Xvfb plugin version 1.0.2
Code changed in jenkins
User: Zoran Regvart
Path:
src/main/java/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper.java
src/main/java/org/jenkinsci/plugins/xvfb/XvfbEnvironment.java
http://jenkins-ci.org/commit/xvfb-plugin/b25ee74766b91b268f740640590f985191323a21
Log:
JENKINS-14483Remaining Xvfb processes in matrix jobsimplemented as kindly suggested by Chris Jonhson on jenkins-dev mailing
list
https://groups.google.com/d/topic/jenkinsci-dev/KQVDCV9ATm8/discussion