• Type: Improvement
• Resolution: Not A Defect
• Priority: Major
• Component/s: xvnc-plugin
• Labels:

  • configuration
  • plugin

[JENKINS-17049] Xvnc "-localhost -nolisten tcp" should be configurable

Collapse comment: Jesse Glick added a comment - 2013-03-04 22:57

Jesse Glick added a comment - 2013-03-04 22:57

Might be better to enhance the plugin with screenshot functionality, so that while the build is running you can grab screenshots (if you are an authorized user; can define a new permission for it). That would allow you to run the plugin securely and avoids the need to have X protocol access to the slave.

Expand comment: Jesse Glick added a comment - 2013-03-04 22:57

Jesse Glick added a comment - 2013-03-04 22:57 Might be better to enhance the plugin with screenshot functionality, so that while the build is running you can grab screenshots (if you are an authorized user; can define a new permission for it). That would allow you to run the plugin securely and avoids the need to have X protocol access to the slave.

Collapse comment: Jesse Glick added a comment - 2013-03-04 22:59

Jesse Glick added a comment - 2013-03-04 22:59

Originally introduced as: http://issues.hudson-ci.org/browse/HUDSON-8670

Expand comment: Jesse Glick added a comment - 2013-03-04 22:59

Jesse Glick added a comment - 2013-03-04 22:59 Originally introduced as: http://issues.hudson-ci.org/browse/HUDSON-8670

Collapse comment: Federico Fissore added a comment - 2013-03-05 08:36

Federico Fissore added a comment - 2013-03-05 08:36

If for "screenshots" you intend "videos" then it answers my needs but introduces an overhead that may no be acceptable. In my case I needed to see the application running because the glitch that caused the build to fail showed just for a moment.

Expand comment: Federico Fissore added a comment - 2013-03-05 08:36

Federico Fissore added a comment - 2013-03-05 08:36 If for "screenshots" you intend "videos" then it answers my needs but introduces an overhead that may no be acceptable. In my case I needed to see the application running because the glitch that caused the build to fail showed just for a moment.

Collapse comment: Jesse Glick added a comment - 2013-03-07 17:08

Jesse Glick added a comment - 2013-03-07 17:08

Was preparing a fix for this when I realized it is unnecessary: just change the Command line in global settings for the plugin to vncserver :$DISPLAY_NUMBER. (The -localhost -nolisten tcp is only part of the default command line, if you have not customized it.)

Expand comment: Jesse Glick added a comment - 2013-03-07 17:08

Jesse Glick added a comment - 2013-03-07 17:08 Was preparing a fix for this when I realized it is unnecessary: just change the Command line in global settings for the plugin to vncserver :$DISPLAY_NUMBER . (The -localhost -nolisten tcp is only part of the default command line, if you have not customized it.)

Collapse comment: Federico Fissore added a comment - 2013-03-07 17:16

Federico Fissore added a comment - 2013-03-07 17:16

soo easy! thank you very much: I confirm it works like a charm!

Expand comment: Federico Fissore added a comment - 2013-03-07 17:16

Federico Fissore added a comment - 2013-03-07 17:16 soo easy! thank you very much: I confirm it works like a charm!