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

JENKINS-70279 regression when using JENKINS_URL with a /suffix

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Minor Minor
    • monitoring-plugin
    • Jenkins 2.452.3 LTS
      Monitoring 1.99.0

      Hello

      Our jenkins is accessible using url jenkins.domain.com/prod

      Was trying today to access the monitoring page of a build agent, from agent page.
      Found out JENKINS-70279 probably introduced a regression, breaking the Build agent monitoring page in our case:

      Most of resources are wrongly served from root url jenkins.domain.com/monitoring, instead of jenkins.domain.com/prod/monitoring, resulting in 404 for all pages.

      Note navigating to monitoring from the main /manage page is still working, but gives less information.

        1. image-2024-10-07-10-41-13-139.png
          image-2024-10-07-10-41-13-139.png
          63 kB

          [JENKINS-73868] JENKINS-70279 regression when using JENKINS_URL with a /suffix

          Geoffroy Jabouley created issue -
          Geoffroy Jabouley made changes -
          Description Original: Hello

          Our jenkins is accessible using url https://jenkins.domain.com/*prod*

          Was trying today to access the monitoring page of a build agent, from agent page.
          Found out [JENKINS-70279|https://issues.jenkins.io/browse/JENKINS-70279] probably introduced a regression, breaking the Build agent monitoring page in our case:
           !image-2024-10-07-10-41-13-139.png|thumbnail!

          Most of resources are wrongly served from root url https://jenkins.domain.com/monitoring, instead of https://jenkins.domain.com/*prod*/monitoring, resulting in 404 for all pages.

          Note navigating to monitoring from the main /manage page is still working, but gives less information.

          		New: Hello

          Our jenkins is accessible using url *jenkins.domain.com/{+}prod{+}*

          Was trying today to access the monitoring page of a build agent, from agent page.
          Found out [JENKINS-70279|https://issues.jenkins.io/browse/JENKINS-70279] probably introduced a regression, breaking the Build agent monitoring page in our case:
          !image-2024-10-07-10-41-13-139.png|thumbnail!

          Most of resources are wrongly served from root url {*}jenkins.domain.com/monitoring{*}, instead of {*}jenkins.domain.com/{+}prod{+}/monitoring{*}, resulting in 404 for all pages.

          Note navigating to monitoring from the main /manage page is still working, but gives less information.

          evernat added a comment -

          fixed by https://github.com/jenkinsci/monitoring-plugin/commit/4bf2ea6

          evernat added a comment - fixed by https://github.com/jenkinsci/monitoring-plugin/commit/4bf2ea6
          evernat made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Fixed but Unreleased [ 10203 ]
          evernat made changes -
          Status Original: Fixed but Unreleased [ 10203 ] New: Resolved [ 5 ]
          evernat made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]

            evernat evernat
            geoffroyjabouley Geoffroy Jabouley
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: