When running the build pipeline and clicking the "console" icon the modal window only shows (in Chrome) "Unable to resolve the server's DNS address." The problem is that clicking on the "console" icon tries to load the following address which obviously doesn't work:

      http://job/JobName/71/console

          [JENKINS-25430] Clicking on "console" icon doesn't work

          Joel Njanga added a comment -

          thanks for your prompt response.
          agreed that this issue is minor in comparison with https://issues.jenkins-ci.org/browse/JENKINS-20873 which definitely does not work with jenkins 1.606 even when dowgradind the plugin to ver 1.4.3

          Joel Njanga added a comment - thanks for your prompt response. agreed that this issue is minor in comparison with https://issues.jenkins-ci.org/browse/JENKINS-20873 which definitely does not work with jenkins 1.606 even when dowgradind the plugin to ver 1.4.3

          emwfrpr added a comment -

          I copied in the 2 corrected files, and it all works perfectly with ver. 1.4.7
          Will there be a new release of the build-pipeline-plugin in the near future ?

          emwfrpr added a comment - I copied in the 2 corrected files, and it all works perfectly with ver. 1.4.7 Will there be a new release of the build-pipeline-plugin in the near future ?

          Vikas Kumar added a comment -

          The solution by Nicolas did not worked for me on Jenkins v1.621-1.1 and Build Pipeline v1.4.7. The console icon is clickable now, but does not show any output.

          I even tried to copy+paste the two files in vain.

          Vikas Kumar added a comment - The solution by Nicolas did not worked for me on Jenkins v1.621-1.1 and Build Pipeline v1.4.7. The console icon is clickable now, but does not show any output. I even tried to copy+paste the two files in vain.

          May be you can try this : in a pipeline-view, clik on "Configure" and at the bottom of the page there is an option called "Console Output Link Style", you can try to change it... I'm not sure //TODO!

          Nicolas BOHEAS added a comment - May be you can try this : in a pipeline-view, clik on "Configure" and at the bottom of the page there is an option called "Console Output Link Style", you can try to change it... I'm not sure //TODO!

          @Vikas Kumar : have a look in javascript console, may be you'll see a message more explicit :/

          Nicolas BOHEAS added a comment - @Vikas Kumar : have a look in javascript console, may be you'll see a message more explicit :/

          Vikas Kumar added a comment -

          niko44 Thanks for the tip . Changing the Console Output Link Style from Lightbox to New Window or Same Window works fine.

          Vikas Kumar added a comment - niko44 Thanks for the tip . Changing the Console Output Link Style from Lightbox to New Window or Same Window works fine.

          Dan Alvizu added a comment -

          Merged to master, fixed in next release (1.4.9)

          Dan Alvizu added a comment - Merged to master, fixed in next release (1.4.9)

          Just tried with 1.4.9 and Jenkins 1.609.2 and this does not appear to be fixed.

          Lance Johnston added a comment - Just tried with 1.4.9 and Jenkins 1.609.2 and this does not appear to be fixed.

          Dan Alvizu added a comment -

          Are you seeing the same error above or a different one? Have you set your jenkins URL in system configuration?

          Dan Alvizu added a comment - Are you seeing the same error above or a different one? Have you set your jenkins URL in system configuration?

          Indeed, the problem turned out to be related to the jenkins URL in the system configuration. Specifically, my apache reverse proxy was down and I was using the direct jenkins url, bypassing the one in the system configuration, when I encountered this problem. Once the reverse proxy was back up, console output started working again.

          Lance Johnston added a comment - Indeed, the problem turned out to be related to the jenkins URL in the system configuration. Specifically, my apache reverse proxy was down and I was using the direct jenkins url, bypassing the one in the system configuration, when I encountered this problem. Once the reverse proxy was back up, console output started working again.

            dalvizu Dan Alvizu
            johanhaleby Johan Haleby
            Votes:
            0 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: