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

Jenkins configure system save button doesn't work after updating to 2.285

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Critical
    • Resolution: Unresolved
    • Component/s: artifactory-plugin
    • Labels:
    • Environment:
      Jenkins server VM details:
      OS: Red Hat Enterprise Linux Server release 7.8 (Maipo)

      Browser tested: Google chrome 89.0.4389.90 and Microsoft Edge Browser
    • Similar Issues:

      Description

      Problem Description:
      We have installed latest artifactory plugin after upgrading our Jenkins from version 2.274 to 2.285.
      When I try to save artifactory server details in the Jenkins > Configure System page, neither save button or apply button works. Looks like they are broken. 

      Steps to replicate the issue

      1. start a clean instance of Jenkins 2.285 or upgrade from a older Jenkins version 2.274 to 2.285.
      2. install  artifactory plugin 3.10.6
      3. restart Jenkins
      4. go to Manage Jenkins/Configure System
      5. Enter artifactory server details like Server ID, URL, Username and Password
      6. click on save
      7. It should return to Manage Jenkins but instead it stays on Manage Jenkins/Configure System and doesn't save changes made.

      We request you to address this asap as we are stuck with out CI/CD pipeline work that has to be implemented for UAT and Prod.

        Attachments

          Activity

          Hide
          sriramperumalla sriram added a comment -

          Hello Jenkins Experts,
          Can I ask you for the update on this issue? We are stuck with jfrog integration with our Jenkins 2.285. Please let me know, if there is a workaround to save button configure system page after entering jfrog settings.

          Thank you,
          Sriram

          Show
          sriramperumalla sriram added a comment - Hello Jenkins Experts, Can I ask you for the update on this issue? We are stuck with jfrog integration with our Jenkins 2.285. Please let me know, if there is a workaround to save button configure system page after entering jfrog settings. Thank you, Sriram
          Hide
          sriramperumalla sriram added a comment -

          Hello Eyal Ben Moshe,

          Can I request you to update on this issue please? Will an upgrade from existing 2.285 version to 2.288 solve the problem?

          Regards,
          Sriram

          Show
          sriramperumalla sriram added a comment - Hello Eyal Ben Moshe , Can I request you to update on this issue please? Will an upgrade from existing 2.285 version to 2.288 solve the problem? Regards, Sriram
          Hide
          sriramperumalla sriram added a comment -

          Hello Eyal Ben Moshe,

          Will this ticket be worked on? or Is it not a bug? Please confirm. If it is not a bug, please give a workaround to save Configure System page settings.

          Regards,

          Sriram

          Show
          sriramperumalla sriram added a comment - Hello Eyal Ben Moshe , Will this ticket be worked on? or Is it not a bug? Please confirm. If it is not a bug, please give a workaround to save Configure System page settings. Regards, Sriram
          Hide
          sriramperumalla sriram added a comment -

          Hello Experts,
          Jenkins Configure System > Save issue is fixed after upgrading the following plugin: https://plugins.jenkins.io/apache-httpcomponents-client-4-api/
           
          You may please close this ticket. Thanks for not responding to my request on time. It helped me learn more and enabled me solve it myself after 20 days of struggle.
           
          Thank you,
          Sriram

          Show
          sriramperumalla sriram added a comment - Hello Experts, Jenkins Configure System > Save issue is fixed after upgrading the following plugin: https://plugins.jenkins.io/apache-httpcomponents-client-4-api/   You may please close this ticket. Thanks for not responding to my request on time. It helped me learn more and enabled me solve it myself after 20 days of struggle.   Thank you, Sriram
          Hide
          stevenc Steven Christenson added a comment -

          This bug was opened under component "artifactory-plugin" thats likely part of the reason it wasn't looked into - although I see evidence from https://issues.jenkins.io/browse/JENKINS-64072 that artifactory plugin is also suspect. We don't have the artifactory-plugin installed.

          For what it's worth, we have the same unable to save configuration problem described here and we are also hamstrung with the latest apache-httpcomponents-client-4-api (4.5.13-1.0) which is a dependency of a LOT of plugins.

          We are running 2.277.4.3-rolling with all the "correct" BeeKeeper recommended plugins.

          Finally apache-httpcomonents-client-4-api is marked "up for adoption" which means it's basically unsupported. So it's scary how a highly required dependency could be "abandoned" by maintainers.

          Show
          stevenc Steven Christenson added a comment - This bug was opened under component "artifactory-plugin" thats likely part of the reason it wasn't looked into - although I see evidence from https://issues.jenkins.io/browse/JENKINS-64072  that artifactory plugin is also suspect. We don't have the artifactory-plugin installed. For what it's worth, we have the same unable to save configuration problem described here and we are also hamstrung with the latest apache-httpcomponents-client-4-api ( 4.5.13-1.0 ) which is a dependency of a LOT of plugins. We are running  2.277.4.3-rolling  with all the "correct" BeeKeeper recommended plugins. Finally apache-httpcomonents-client-4-api is marked "up for adoption" which means it's basically unsupported. So it's scary how a highly required dependency could be "abandoned" by maintainers.
          Hide
          markewaite Mark Waite added a comment - - edited

          Steven Christenson there are many different ways that a tables to div issue could prevent saving a Jenkins job configuration or global configuration.

          Getting help with the specific issue you're seeing requires specific steps to duplicate the problem and a specific, detailed list of the exact plugins and versions installed in Jenkins. There is a groovy script that will output the plugin names and versions in a format that others can use to help diagnose the issue.

          You mentioned that you believe it is somehow related to apache-httpcomponents-client-4-api. I've not seen any cases where that API plugin was related in any way to a failure to save a Jenkins configuration form. I realize that sriram says that the issue was resolved by an upgrade to apache http components plugin yet the most recent release of that plugin was over 5 months ago and the changelogs for the releases from the last two years do not mention anything that would suggest to me that it would alter the saving of HTML forms. I suspect that the "upgrade" that fixed sriram was also an upgrade of some other plugin that needed a fix for tables to divs. Can you describe further why you believe that apache http components it is related to the problem you're seeing?

          It is usually best to provide a new bug report for this type of issue, rather than commenting on an existing bug report. This bug report is specific to the artifactory plugin. Since you say that you do not have the artifactory plugin, this bug does not describe your case. The new bug report needs to include the precise list of plugins that are installed, the version numbers of those plugins, and the detailed steps required for another persons to see the problem that you're seeing.

          You suggested that "up for adoption" means a plugin is "basically unsupported". That's not really the case, especially in the case of an API plugin like the Apache HTTP components API plugin. A plugin that is "up for adoption" has been noted by the maintainer that they would like help from others to maintain the plugin. The apache http components plugin 4.5.13 matches the Apache HTTP components API 4.5.13 release. That is the most recent release of the Apache HTTP 4.5 library. The Apache HTTP Components status page describes the 4.5 series as:

          HttpClient 4.5.x branch is considered stable and production ready. While being actively maintained and supported, the 4.x release series will be receiving fixes for major defects and security issues only.

          Yes, we'd love to have more maintainers, but since that API plugin is synchronized with its matching upstream release, I don't see that as a cause for concern.

          You mentioned that you're running 2.277.4.3. That's a CloudBees version number. That usually means you have a support contract with CloudBees and can request help from the CloudBees support team.

          Show
          markewaite Mark Waite added a comment - - edited Steven Christenson there are many different ways that a tables to div issue could prevent saving a Jenkins job configuration or global configuration. Getting help with the specific issue you're seeing requires specific steps to duplicate the problem and a specific, detailed list of the exact plugins and versions installed in Jenkins. There is a groovy script that will output the plugin names and versions in a format that others can use to help diagnose the issue. You mentioned that you believe it is somehow related to apache-httpcomponents-client-4-api. I've not seen any cases where that API plugin was related in any way to a failure to save a Jenkins configuration form. I realize that sriram says that the issue was resolved by an upgrade to apache http components plugin yet the most recent release of that plugin was over 5 months ago and the changelogs for the releases from the last two years do not mention anything that would suggest to me that it would alter the saving of HTML forms. I suspect that the "upgrade" that fixed sriram was also an upgrade of some other plugin that needed a fix for tables to divs. Can you describe further why you believe that apache http components it is related to the problem you're seeing? It is usually best to provide a new bug report for this type of issue, rather than commenting on an existing bug report. This bug report is specific to the artifactory plugin. Since you say that you do not have the artifactory plugin, this bug does not describe your case. The new bug report needs to include the precise list of plugins that are installed, the version numbers of those plugins, and the detailed steps required for another persons to see the problem that you're seeing. You suggested that "up for adoption" means a plugin is "basically unsupported". That's not really the case, especially in the case of an API plugin like the Apache HTTP components API plugin. A plugin that is "up for adoption" has been noted by the maintainer that they would like help from others to maintain the plugin. The apache http components plugin 4.5.13 matches the Apache HTTP components API 4.5.13 release. That is the most recent release of the Apache HTTP 4.5 library. The Apache HTTP Components status page describes the 4.5 series as: HttpClient 4.5.x branch is considered stable and production ready. While being actively maintained and supported, the 4.x release series will be receiving fixes for major defects and security issues only. Yes, we'd love to have more maintainers, but since that API plugin is synchronized with its matching upstream release, I don't see that as a cause for concern. You mentioned that you're running 2.277.4.3. That's a CloudBees version number. That usually means you have a support contract with CloudBees and can request help from the CloudBees support team.

            People

            Assignee:
            eyalbe Eyal Ben Moshe
            Reporter:
            sriramperumalla sriram
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated: