-
Bug
-
Resolution: Won't Fix
-
Major
-
None
-
linux
In our jenkins configuration we have several slaves on the same linux server and we have some jobs that run on these slaves.
Because each slave has just a single executor, when we try to run the job with Xvfb plugin, all slaves try to run with the same display and therefore fail.
[JENKINS-18607] Xvfb plugin doesn't work on matrix jobs with slaves on the same machine
Code changed in jenkins
User: takeuchi
Path:
src/main/java/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper.java
src/main/java/org/jenkinsci/plugins/xvfb/XvfbDisplayAllocator.java
src/main/java/org/jenkinsci/plugins/xvfb/XvfbEnvironment.java
src/main/resources/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper/config.jelly
src/main/resources/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper/global.jelly
src/main/resources/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper/help-assignRandomDisplay.html
src/main/resources/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper/help-maxDisplayNumber.html
src/main/resources/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper/help-minDisplayNumber.html
http://jenkins-ci.org/commit/xvfb-plugin/466bef4983d770e26ff616a34126d8710f90b3be
Log:
JENKINS-18607 Adding an option that uses the exact same strategy from the Xvnc plugin to find random and available display numers
Code changed in jenkins
User: takeuchi
Path:
src/main/java/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper.java
src/main/java/org/jenkinsci/plugins/xvfb/XvfbDisplayAllocator.java
src/main/java/org/jenkinsci/plugins/xvfb/XvfbEnvironment.java
src/main/resources/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper/config.jelly
src/main/resources/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper/global.jelly
src/main/resources/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper/help-assignRandomDisplay.html
src/main/resources/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper/help-maxDisplayNumber.html
src/main/resources/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper/help-minDisplayNumber.html
http://jenkins-ci.org/commit/xvfb-plugin/2f8cbf32b88fb50c744a1dd749fbd6b9eee97065
Log:
JENKINS-18607 Adding an option that uses the exact same strategy from the Xvnc plugin to find random and available display numers
Code changed in jenkins
User: takeuchi
Path:
pom.xml
src/main/java/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper.java
http://jenkins-ci.org/commit/xvfb-plugin/2f536ed7432d270b9726dd3a3b1c6905cc92b3d6
Log:
JENKINS-18607 Fixed problems with concurrent when launching Xvfb
Code changed in jenkins
User: takeuchi
Path:
src/main/java/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper.java
src/main/java/org/jenkinsci/plugins/xvfb/XvfbDisplayAllocator.java
src/main/resources/org/jenkinsci/plugins/xvfb/Messages.properties
src/main/resources/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper/config.jelly
http://jenkins-ci.org/commit/xvfb-plugin/b67a13e71f768a06da573f6ff82662e009d1bdf5
Log:
JENKINS-18607 Fixed problems with concurrent when launching Xvfb
Code changed in jenkins
User: Zoran Regvart
Path:
src/main/java/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper.java
src/main/resources/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper/config.jelly
src/main/resources/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper/help-useNodeOffsets.html
http://jenkins-ci.org/commit/xvfb-plugin/61ca30dec1da9e4f2cef85b995f0806f35a66b7c
Log:
JENKINS-18607 Xvfb plugin doesn't work on matrix jobs with slaves on the
same machine
Code changed in jenkins
User: Zoran Regvart
Path:
src/main/java/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper.java
src/main/resources/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper/config.jelly
src/main/resources/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper/help-useNodeOffsets.html
http://jenkins-ci.org/commit/xvfb-plugin/2b652cd0785a4bb09f98bac0319811b0aa87aad6
Log:
Revert "JENKINS-18607 Xvfb plugin doesn't work on matrix jobs with slaves on the"
This reverts commit 61ca30dec1da9e4f2cef85b995f0806f35a66b7c.
zregvart
added a comment - There is a new option for the Xvfb plugin that uses the -displayfd option of the Xvfb. This basically lets the Xvfb to pick its own display name and returns it via stderr to the Xvfb Jenkins plugin. In this case Xvfb tries to find a free display name by scanning for a free one.
With this feature there is no need for the plugin to scan for a free display name, as this is done by Xvfb.
zregvart
added a comment - There is a new option for the Xvfb plugin that uses the -displayfd option of the Xvfb. This basically lets the Xvfb to pick its own display name and returns it via stderr to the Xvfb Jenkins plugin. In this case Xvfb tries to find a free display name by scanning for a free one.
With this feature there is no need for the plugin to scan for a free display name, as this is done by Xvfb. zregvart
added a comment - Just to note that in order to use this new feature there is a beta version available in the experimental update site (http://updates.jenkins-ci.org/experimental/update-center.json). See http://jenkins-ci.org/node/439 for instructions on how to setup.
zregvart
added a comment - Just to note that in order to use this new feature there is a beta version available in the experimental update site ( http://updates.jenkins-ci.org/experimental/update-center.json ). See http://jenkins-ci.org/node/439 for instructions on how to setup. 
Just to mention, Xvnc's plugin address this problem by trying to guess which displays are under use and try a different display number. Perhaps you could try a similar strategy.