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

The "Configure Now" and "Uninstall Plugin" administrative monitors are broken

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • None

      With the steps described in the `Environment` field, When clicking the "Configure Now" or "Uninstall Plugin" buttons in the administrative monitor for Jenkins Health Advisor by CloudBees plugin, the buttons do nothing.

      Usually these buttons send you to
      JENKINS_URL/manage/cloudbees-jenkins-advisor/
      JENKINS_URL/pluginManager/installed

      But the buttons are no longer working.

          [JENKINS-71651] The "Configure Now" and "Uninstall Plugin" administrative monitors are broken

          Mark Waite added a comment -

          rkivisto I'm curious about the source of the issue. Jenkins 2.401.2 contains Prototype.js and does not have the flag to remove it, yet the plugin behaves incorrectly with 2.401.2. I assume that means the issue is in the Jenkins health adviser plugin, not in Jenkins core. However, you say that your workaround was to enable and then disable the "Remove Prototype.js" experiment so that Prototype.js was not installed in your running Jenkins controller. That seems to be as though the end state of your workaround still had Prototype.js enabled and available in the controller. I don't see how that is different from the 2.401.2 condition.

          Can you help me understand?

          Mark Waite added a comment - rkivisto I'm curious about the source of the issue. Jenkins 2.401.2 contains Prototype.js and does not have the flag to remove it, yet the plugin behaves incorrectly with 2.401.2. I assume that means the issue is in the Jenkins health adviser plugin, not in Jenkins core. However, you say that your workaround was to enable and then disable the "Remove Prototype.js" experiment so that Prototype.js was not installed in your running Jenkins controller. That seems to be as though the end state of your workaround still had Prototype.js enabled and available in the controller. I don't see how that is different from the 2.401.2 condition. Can you help me understand?

          Ray Kivisto added a comment -

          I just re-tested after cleaning my workspace, and the prototype.js flag is not affecting the feature anymore, so I'm updating the description of the issue to exclude the Prototype.js changes as the cause.

          Ray Kivisto added a comment - I just re-tested after cleaning my workspace, and the prototype.js flag is not affecting the feature anymore, so I'm updating the description of the issue to exclude the Prototype.js changes as the cause.

          This has apparently been broken since before 2.401.. Quickly testing a few LTS, it works in 2.375.1 but not in 2.387.1.

          Allan BURDAJEWICZ added a comment - This has apparently been broken since before 2.401.. Quickly testing a few LTS, it works in 2.375.1 but not in 2.387.1.

          Pierre Beitz added a comment - - edited

          The monitors are working in 2.375, not in 2.376.

          Given the range, the only change that explains this regression is https://github.com/jenkinsci/jenkins/pull/7203.

          With that in mind, I think I'll accept both PRs since it  fixes the issue by using an approach present in core.

          Pierre Beitz added a comment - - edited The monitors are working in 2.375, not in 2.376. Given the range, the only change that explains this regression is https://github.com/jenkinsci/jenkins/pull/7203 . With that in mind, I think I'll accept both PRs since it  fixes the issue by using an approach present in core.

            rkivisto Ray Kivisto
            rkivisto Ray Kivisto
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: