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

Save and Apply buttons doesn't work for "Configuration system"

      We see that save/Apply buttons doesnt work in configuration system page, it doesnt throw any errors too, but it doesnt work.

       

      Attaching the list of plugins used by us and a screenshot for reference

          [JENKINS-67668] Save and Apply buttons doesn't work for "Configuration system"

          Mark Waite added a comment -

          Please refer to https://community.jenkins.io/t/migrating-jenkins/894/5 for detailed steps you should take to evaluate your own installation. Once those detailed steps are complete, please update the issue with the additional information from your exploration.

          Mark Waite added a comment - Please refer to https://community.jenkins.io/t/migrating-jenkins/894/5 for detailed steps you should take to evaluate your own installation. Once those detailed steps are complete, please update the issue with the additional information from your exploration.

          Hi markewaite

          We tried updating the plugins and removing the unused ones, but still the error persists, Also the configure page there is  difference in alignment post the second half of the page. Attaching the screen shot for reference.

          Kiruthika Subramaniam added a comment - Hi markewaite We tried updating the plugins and removing the unused ones, but still the error persists, Also the configure page there is  difference in alignment post the second half of the page. Attaching the screen shot for reference.

          Mark Waite added a comment - - edited

          kiruthisubbu if you upgraded the plugins, then you did not update the list of installed versions that you provided in Jenkins_Plugin.txt because there are several plugins in that list that are not the current release. For example:

          • You list scm-api 2.6.5, but 595.vd5a_df5eb_0e39 is the current version, released 20 days ago
          • You list schedule-build 0.5.1 but the 178.v32999348869c is the current version, released 3 months ago
          • You list git plugin 4.8.2 but 4.10.3 is the current version, released a week ago
          • You list subversion plugin 2.14.4 but 2.15.2 is the current version, released 2 weeks ago

          If you followed all the steps in https://community.jenkins.io/t/migrating-jenkins/894/5, then you missed that the job direct mail plugin is in the list of plugins known to have issues with configuration form modernization. JENKINS-65478 and JENKINS-65887 both document that in the list of plugins with known issues., You'll need to remove that plugin or adopt the plugin and fix it.

          You're running an unreleased version of the project stats plugin. The last release was 9 years ago. That plugin may have issues with configuration form modernization.

          Please update the list of plugins installed and provide the list in the format described in the links available from https://community.jenkins.io/t/migrating-jenkins/894/5 so that others will be more willing to help you.

          You're using private builds of at least two plugins, tnpublisher and project-stats-plugin. Others do not have access to your private builds of those plugins. You'll need to remove them.

          Your list includes several plugins that are not available from the Jenkins update center, including jenkins-dive, tnpublisher, sdlmahud. You'll need to remove them.

          Mark Waite added a comment - - edited kiruthisubbu if you upgraded the plugins, then you did not update the list of installed versions that you provided in Jenkins_Plugin.txt because there are several plugins in that list that are not the current release. For example: You list scm-api 2.6.5, but 595.vd5a_df5eb_0e39 is the current version, released 20 days ago You list schedule-build 0.5.1 but the 178.v32999348869c is the current version, released 3 months ago You list git plugin 4.8.2 but 4.10.3 is the current version, released a week ago You list subversion plugin 2.14.4 but 2.15.2 is the current version, released 2 weeks ago If you followed all the steps in https://community.jenkins.io/t/migrating-jenkins/894/5 , then you missed that the job direct mail plugin is in the list of plugins known to have issues with configuration form modernization. JENKINS-65478 and JENKINS-65887 both document that in the list of plugins with known issues., You'll need to remove that plugin or adopt the plugin and fix it. You're running an unreleased version of the project stats plugin. The last release was 9 years ago. That plugin may have issues with configuration form modernization. Please update the list of plugins installed and provide the list in the format described in the links available from https://community.jenkins.io/t/migrating-jenkins/894/5 so that others will be more willing to help you. You're using private builds of at least two plugins, tnpublisher and project-stats-plugin. Others do not have access to your private builds of those plugins. You'll need to remove them. Your list includes several plugins that are not available from the Jenkins update center, including jenkins-dive, tnpublisher, sdlmahud. You'll need to remove them.

          Mark Waite added a comment -

          I was interested in the set of plugins that you had provided in case there was a new discovery related to configuration form modernization. I was able to duplicate the problem with the plugins you listed.

          I applied the instructions at https://community.jenkins.io/t/migrating-jenkins/894/5 and:

          1. removed the plugins that are not available (like jenkins-dive, tnpublisher, sdlmahud, and ruby-runtime),
          2. removed the plugins that have security warnings (like build-metrics, build-pipeline, buildgraph-view, dynamic_extended_choice_parameter, ldapemail, mailcommander, performance, radiatorviewplugin, and sms),
          3. removed the plugins that are known to have issues with configuration form modernization (like job direct mail, gerrit-trigger),

          and confirmed that system configuration save works.

          I wish you had done that work yourself, since it is very instructive to follow those steps and see all the things that can and should be removed. There are still many plugins in your configuration that I am confident are unused. For example, the ui-samples plugin is not likely to be used in a production environment.

          I've uploaded the plugin names and versions that I used as plugins.txt.

          Mark Waite added a comment - I was interested in the set of plugins that you had provided in case there was a new discovery related to configuration form modernization. I was able to duplicate the problem with the plugins you listed. I applied the instructions at https://community.jenkins.io/t/migrating-jenkins/894/5 and: removed the plugins that are not available (like jenkins-dive, tnpublisher, sdlmahud, and ruby-runtime), removed the plugins that have security warnings (like build-metrics, build-pipeline, buildgraph-view, dynamic_extended_choice_parameter, ldapemail, mailcommander, performance, radiatorviewplugin, and sms), removed the plugins that are known to have issues with configuration form modernization (like job direct mail, gerrit-trigger), and confirmed that system configuration save works. I wish you had done that work yourself, since it is very instructive to follow those steps and see all the things that can and should be removed. There are still many plugins in your configuration that I am confident are unused. For example, the ui-samples plugin is not likely to be used in a production environment. I've uploaded the plugin names and versions that I used as plugins.txt .

          Mark Waite added a comment -

          Duplicate of the issue reports for job direct mail plugin and gerrit trigger plugin

          Mark Waite added a comment - Duplicate of the issue reports for job direct mail plugin and gerrit trigger plugin

          Thanks markewaite I have disabled below plugins and the save issue is resolved now 

          job-direct-mail.jpi.disabled
          jenkins-dive.hpi.disabled
          tnpublisher.hpi.disabled
          sdlmahud.hpi.disabled
          ruby-runtime.jpi.disabled

          Kiruthika Subramaniam added a comment - Thanks markewaite  I have disabled below plugins and the save issue is resolved now  job-direct-mail.jpi.disabled jenkins-dive.hpi.disabled tnpublisher.hpi.disabled sdlmahud.hpi.disabled ruby-runtime.jpi.disabled

          Mark Waite added a comment -

          The job direct email plugin has been suspended from distribution because it breaks global configuration save.

          Mark Waite added a comment - The job direct email plugin has been suspended from distribution because it breaks global configuration save.

            Unassigned Unassigned
            kiruthisubbu Kiruthika Subramaniam
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: