-
Improvement
-
Resolution: Not A Defect
-
Major
Currently, the xvfb plugin always starts without a window manager. This causes errors/problems with the focus change in some test libraries like Fest (using the java.awt.robot).
If you start a window manager yourself between xvfb and the surefire plugin, the errors are gone.
It would be great if you would have a textfield in the global configuration of the plugin, where you can execute a program/window manager after xvfb is started. I am not sure that the display variable has to be exported for it to work.
Currently, running this before our tests and after xvfb has started prevents the errors:
export DISPLAY=:99 twm &
- is duplicated by
-
-
- Closed
-
[JENKINS-19006] Add option to start a program/windowmanager with Xvfb
The xvfb plugin shies away from doing anything more than controlling the Xvfb. This kind of requirement is better handled by Execute shell build step in a freestyle project. If you feel that this needs to be a feature of the xvfb plugin, please reopen the JENKINS-17308 issue that speaks broadly about launching any program after Xvfb is started.
zregvart
added a comment - - edited The xvfb plugin shies away from doing anything more than controlling the Xvfb. This kind of requirement is better handled by Execute shell build step in a freestyle project. If you feel that this needs to be a feature of the xvfb plugin, please reopen the JENKINS-17308 issue that speaks broadly about launching any program after Xvfb is started. 
Similar requirement