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

Wrong port numbers in hyperlinks, case 8211

    Details

    • Similar Issues:

      Description

      1. On the console output, at the bottom, when the job reports the hyperlinks of downstream jobs, the link is broken.This is specifically in a case where I customized the port number Jenkins is running on. I changed it to 8081, but these links still have 8080 in them. Other than that they are fine.

      2. If you are using the Next Executions plugin, the links on the lower left of home page which tell you about the next scheduled job(s), also have the wrong port number so the link is broken

        Attachments

          Activity

          Hide
          pulak Pulak Agrawal added a comment -

          Same for me + If you are using the Next Executions plugin, the links on the lower left of home page which tell you about the next scheduled job(s), also have the wrong port number.

          Show
          pulak Pulak Agrawal added a comment - Same for me + If you are using the Next Executions plugin, the links on the lower left of home page which tell you about the next scheduled job(s), also have the wrong port number.
          Hide
          wolfgang Christian Wolfgang added a comment -

          Ok, good point, I will look at it.

          Show
          wolfgang Christian Wolfgang added a comment - Ok, good point, I will look at it.
          Hide
          wolfgang Christian Wolfgang added a comment -

          Ok, I was a bit tired yesterday, but I'm not sure this is related to the logging plugin!? I guess I didn't read the description to careful!

          I'll resolve it. Please either reopen the issue again if you are sure it's about the logging plugin or change the component to the correct one.

          Show
          wolfgang Christian Wolfgang added a comment - Ok, I was a bit tired yesterday, but I'm not sure this is related to the logging plugin!? I guess I didn't read the description to careful! I'll resolve it. Please either reopen the issue again if you are sure it's about the logging plugin or change the component to the correct one.

            People

            • Assignee:
              praqma Praqma Support
              Reporter:
              chadmichael chad davis
            • Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: