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

XVnc plugin fails to set the DISPLAY variable properly if jenkins already

XMLWordPrintable

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

      If jenkins already hase the environment variable DISPLAY set then a job using the Xvnc plugin will see this global value instead of the one that Xvnc chooses.

      Example:
      I upgraded jenkins by doing an ssh to the master and running "sudo apt-get install jenkins". Because ssh forwards X the DISPLAY variable was set to "localhost:10" in jenkins.

      When Xvnc now runs the job it chooses a different value for DISPLAY, say "localhost:45". However, the job still sees the value "localhost:10" and fails because this is not a usable display.

          [JENKINS-20177] XVnc plugin fails to set the DISPLAY variable properly if jenkins already

          Levon Saldamli added a comment -

          I cannot reproduce this. I can see the original variable in the environment, but it is reset by the plugin to the correct xvnc display value, as I can see by running "echo $DISPLAY" in a build step shell command. Is this still an issue? Can you provide logs or do a similar test as I did?

          Levon Saldamli added a comment - I cannot reproduce this. I can see the original variable in the environment, but it is reset by the plugin to the correct xvnc display value, as I can see by running "echo $DISPLAY" in a build step shell command. Is this still an issue? Can you provide logs or do a similar test as I did?

          sravanti v added a comment -

          Any updates on this Issue? I see the same issue. It can be reporduced if you have both Environment Injector Plugin and XVnc plugin.
          "echo $DISPLAY" in a build step gives the value from the environment variable, not the DISPLAY set by Xvnc

          sravanti v added a comment - Any updates on this Issue? I see the same issue. It can be reporduced if you have both Environment Injector Plugin and XVnc plugin. "echo $DISPLAY" in a build step gives the value from the environment variable, not the DISPLAY set by Xvnc

          Oliver Gondža added a comment - - edited

          This is a problem in core (JENKINS-25946) where build variables are overridden by slave variables. Actually no, I was not able to reproduce that either.

          Oliver Gondža added a comment - - edited This is a problem in core ( JENKINS-25946 ) where build variables are overridden by slave variables. Actually no, I was not able to reproduce that either.

          Oliver Gondža added a comment -

          This is likely problem in envinject plugin: JENKINS-26583.

          Oliver Gondža added a comment - This is likely problem in envinject plugin: JENKINS-26583 .

            levsa Levon Saldamli
            mhans Martin Hans
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: