-
Bug
-
Resolution: Fixed
-
Major
-
None
-
java -version
openjdk version "11.0.18" 2023-01-17
OpenJDK Runtime Environment Temurin-11.0.18+10 (build 11.0.18+10)
OpenJDK 64-Bit Server VM Temurin-11.0.18+10 (build 11.0.18+10, mixed mode)
a fresh install of Jenkins 2.401.2 LTS
choosing to install no plugins during the wizard
installing Health Advisor by CloudBees (https://plugins.jenkins.io/cloudbees-jenkins-advisor/) Version 336.v4d00382fe22cjava -version openjdk version "11.0.18" 2023-01-17 OpenJDK Runtime Environment Temurin-11.0.18+10 (build 11.0.18+10) OpenJDK 64-Bit Server VM Temurin-11.0.18+10 (build 11.0.18+10, mixed mode) a fresh install of Jenkins 2.401.2 LTS choosing to install no plugins during the wizard installing Health Advisor by CloudBees ( https://plugins.jenkins.io/cloudbees-jenkins-advisor/ ) Version 336.v4d00382fe22c
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.
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?