Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-7093

Block until Xvnc server has finished starting-up

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major Major
    • xvnc-plugin
    • None

      It would be useful if the Xvnc plugin could block until the Xvnc server has finished starting-up, rather than passing control to the next plugin immediately.

      This would be useful for applications that are started at the beginning of the build, or by other plugins. To give one example, see the Android Emulator plugin (and associated JENKINS-6912).

      Possibly we could keep polling TCP port (5900 + $DISPLAY) until it becomes bound, and block until then (or time out)?

      I'm not sure whether there can be a universal solution for all VNC servers (e.g. do they all use TCP?), I but thought I'd put it in JIRA and see if there's any opinion.

          [JENKINS-7093] Block until Xvnc server has finished starting-up

          Jesse Glick added a comment -

          vncserver :66 should not exit until it is really listening on port 5966 in my experience. Is this still reproducible? Is there a test case?

          Jesse Glick added a comment - vncserver :66 should not exit until it is really listening on port 5966 in my experience. Is this still reproducible? Is there a test case?

            Unassigned Unassigned
            orrc Christopher Orr
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: