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

          Ray Kivisto created issue -
          Ray Kivisto made changes -
          Assignee New: Ray Kivisto [ rkivisto ]
          Ray Kivisto made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Ray Kivisto made changes -
          Status Original: In Progress [ 3 ] New: In Review [ 10005 ]
          Ray Kivisto made changes -
          Remote Link New: This issue links to "https://github.com/jenkinsci/cloudbees-jenkins-advisor-plugin/pull/191 (Web Link)" [ 28816 ]
          Mark Waite made changes -
          Summary Original: The "Configure Now" and "Uninstall Plugin" administrative monitors are broken due to Prototype.js removal New: The "Configure Now" and "Uninstall Plugin" administrative monitors are broken if Prototype.js is removed
          Mark Waite made changes -
          Summary Original: The "Configure Now" and "Uninstall Plugin" administrative monitors are broken if Prototype.js is removed New: The "Configure Now" and "Uninstall Plugin" administrative monitors are broken due to Prototype.js removal
          Ray Kivisto made changes -
          Summary Original: The "Configure Now" and "Uninstall Plugin" administrative monitors are broken due to Prototype.js removal New: The "Configure Now" and "Uninstall Plugin" administrative monitors are broken after removal of Prototype.js

          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 made changes -
          Epic Link Original: JENKINS-70906 [ 218261 ]

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

              Created:
              Updated:
              Resolved: