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

Jenkins doesn't save newly created jobs or changes to previously created jobs when clicking Save/Apply buttons

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      When I try to save a newly created job by clicking either the Save or Apply buttons, I do not
      receive a green message saying that the job configuration has been saved. It just leaves me in the job and doesn't retain any changes. Normally when the Apply button is clicked it presents a green message saying that it is saved. And normally when clicking the Save button it exits from the created job and back to the main job window. None of which is happening at this moment and not sure why.

      This is also happening when we attempt to clone prior existing jobs. We cannot make any new changes to jobs as they're not being saved. We just updated our Jenkins release from v2.263.4-1.1 to 2.277.1-1.1. I have attached the jenkins log file and screenshots of how it should normally work when clicking these buttons on job creation and/or configuration. I've also attached screenshots of what is actually happening when we click the Save/Apply buttons during job creation and/or editing a previously created job. This is a major blocker as we cannot create, clone, modify, new and existing jobs currently in Jenkins.

      Just FYI - I scoured and parsed through all the current Jenkins issues to date and could not find any issue related to what we're currently experiencing.

      The deprecated coding-webhook plugin was the root cause of the issue..

      As noted in the 2.277.1 upgrade guide and changelog, please remove deprecated plugins. Please remove plugins with known security issues. Please remove plugins that are unused.

        Attachments

        1. 2021-04-21_13-47.png
          2021-04-21_13-47.png
          24 kB
        2. Folders Plugin.PNG
          Folders Plugin.PNG
          14 kB
        3. image-2021-05-24-10-17-07-903.png
          image-2021-05-24-10-17-07-903.png
          32 kB
        4. Installed Plugins. SJ.docx
          362 kB
        5. Jenkins.png
          Jenkins.png
          22 kB
        6. Jenkins job not working.PNG
          Jenkins job not working.PNG
          19 kB
        7. Jenkins job working.PNG
          Jenkins job working.PNG
          29 kB
        8. jenkins-log.zip
          757 kB
        9. Jenkins not working with Binding section on Job.PNG
          Jenkins not working with Binding section on Job.PNG
          20 kB
        10. Not working when clicking Apply button.PNG
          Not working when clicking Apply button.PNG
          89 kB
        11. Not working when clicking Save button.PNG
          Not working when clicking Save button.PNG
          89 kB
        12. plugins.txt
          6 kB
        13. plugins-working.txt
          6 kB
        14. plugin updates tab.PNG
          plugin updates tab.PNG
          81 kB
        15. Working when clicking Apply button.PNG
          Working when clicking Apply button.PNG
          81 kB
        16. Working when clicking Save button.PNG
          Working when clicking Save button.PNG
          105 kB

          Issue Links

            Activity

            Hide
            markewaite Mark Waite added a comment - - edited

            shri you said:

            WE have installed Jnekins 2.303.1 as the changelog for the versions said that this issue is fixed, however it is not fixed

            Please provide the details of the location in the 2.303.1 changelog that claims "this issue is fixed". There is no reference to this issue in the changelog or in the upgrade guide.

            The list of plugins that you uploaded ( Installed Plugins. SJ.docx ) is unusable for others who might want to help you. If you'd like help from others, please follow the instructions at "How to report an issue", especially the part that describes how to provide a precise list of the plugins you have installed and their versions. The list you provided uses a format that is difficult to read, does not have version numbers, and uses the display name of the plugin instead of the plugin identifier.

            Based on the list, I assume that "Build Time Blame" plugin in your list will have tables to divs issues, since https://github.com/jenkinsci/build-time-blame-plugin/search?q=%3Ctable shows that it uses table markup for at least one of its actions. Remove that plugin and see if it helps .

            The checkstyle plugin has reached end of life. Remove it.

            The job direct mail plugin is known to have tables to divs issues. Remove it.

            You said:

            I went through the suggested steps over different tickets in regards to this issue and followed suggestion but no resolution so far.

            As far as I can tell, your installed list of plugins indicates you did not follow the instructions in other issue reports or the instructions in this issue report.

            To reiterate, those instructions are:

            Perform the steps described in the Jenkins 2.277.1 upgrade guide and in the Jenkins 2.277.1 upgrade webinar so that you can identify the plugin or plugins causing the issue yourself. Those steps are:

            • Upgrade all plugins to latest releases
            • Remove plugins with security issues (like TFS)
            • Remove deprecated plugins (like checkstyle, mulitple scms, pmd, etc.)
            • Remove unused plugins (like CVS, Subversion, Ivy, External Monitor Job Type, etc.)
            • Remove plugins with known issues in tables to divs (like job direct mail plugin)

            If those steps are not enough to resolve the issue, see the instructions at https://www.jenkins.io/doc/developer/views/table-to-div-migration/#identifying-the-broken-plugin .

            If the steps on that page are not enough to resolve the issue, then open a new issue report with the precise list of plugin names and versions, as generated by https://www.jenkins.io/doc/book/system-administration/diagnosing-errors/#how-to-report-a-bug

            Show
            markewaite Mark Waite added a comment - - edited shri you said: WE have installed Jnekins 2.303.1 as the changelog for the versions said that this issue is fixed, however it is not fixed Please provide the details of the location in the 2.303.1 changelog that claims "this issue is fixed". There is no reference to this issue in the changelog or in the upgrade guide. The list of plugins that you uploaded ( Installed Plugins. SJ.docx ) is unusable for others who might want to help you. If you'd like help from others, please follow the instructions at "How to report an issue" , especially the part that describes how to provide a precise list of the plugins you have installed and their versions. The list you provided uses a format that is difficult to read, does not have version numbers, and uses the display name of the plugin instead of the plugin identifier. Based on the list, I assume that "Build Time Blame" plugin in your list will have tables to divs issues, since https://github.com/jenkinsci/build-time-blame-plugin/search?q=%3Ctable shows that it uses table markup for at least one of its actions. Remove that plugin and see if it helps . The checkstyle plugin has reached end of life. Remove it. The job direct mail plugin is known to have tables to divs issues. Remove it. You said: I went through the suggested steps over different tickets in regards to this issue and followed suggestion but no resolution so far. As far as I can tell, your installed list of plugins indicates you did not follow the instructions in other issue reports or the instructions in this issue report . To reiterate, those instructions are: Perform the steps described in the Jenkins 2.277.1 upgrade guide and in the Jenkins 2.277.1 upgrade webinar so that you can identify the plugin or plugins causing the issue yourself. Those steps are: Upgrade all plugins to latest releases Remove plugins with security issues (like TFS) Remove deprecated plugins (like checkstyle, mulitple scms, pmd, etc.) Remove unused plugins (like CVS, Subversion, Ivy, External Monitor Job Type, etc.) Remove plugins with known issues in tables to divs (like job direct mail plugin) If those steps are not enough to resolve the issue, see the instructions at https://www.jenkins.io/doc/developer/views/table-to-div-migration/#identifying-the-broken-plugin . If the steps on that page are not enough to resolve the issue, then open a new issue report with the precise list of plugin names and versions, as generated by https://www.jenkins.io/doc/book/system-administration/diagnosing-errors/#how-to-report-a-bug
            Hide
            clsmith4 Charles Smith added a comment -

            Mark Waite - As a quick update, we managed to get past this issue successfully by completely removing all references/traces to the coding-webhook plugin and by also upgrading to Jenkins version 2.303.2. I would've replied earlier, but I wanted to confirm that the upgrade from 2.263.4 to 2.303.2 fixed the Global configuration save/apply binding issues for us. (i.e. - Global Security/Configure System/etc.)

            Once we were able to generate a complete list of plugins that were unique only to the problematic Jenkins master, we installed those same plugins on a separate test Jenkins master and starting uninstalling/removing those specific plugins one by one. By completely removing all references of the coding-webhook plugin, we were able to successfully save/apply new binding changes to all Jenkins jobs again.

            I should note that the coding-webhook plugin was previously uninstalled during the earlier plugin troubleshooting efforts, but the plugin's homedir under ${JENKINS_HOME/plugins} was still present along with other recursive references to the plugin's .JPI file under ${JENKINS_HOME}. The strange part is that the actual .JPI file was completely removed during the initial plugin uninstall and wasn't found anywhere under the ${JENKINS_HOME} which was a red flag. Another giveaway for us was intermittent error messages about the coding-webhook plugin were observed from time-to-time while refreshing the installed plugins list in the Jenkins UI after a restart of Jenkins. It wasn't a continuous error message and would go away after a certain amount of time, but would show up at the bottom of page after restarting Jenkins and then immediately refreshing the installed plugins list afterwards.

            While removing all references of the coding-webhook plugin resolved the save/apply Jenkins jobs issue, we had to wait until upgrading to version 2.303.2 to officially confirm that the global save/apply binding issues that we encountered had been resolved for us.

            Thank you Mark Waite and everyone else that took the time to reply for helping to guide us with the direction on troubleshooting, diagnosing and ultimately getting us past these issues!

            Show
            clsmith4 Charles Smith added a comment - Mark Waite  - As a quick update, we managed to get past this issue successfully by completely removing all references/traces to the coding-webhook plugin and by also upgrading to Jenkins version 2.303.2 . I would've replied earlier, but I wanted to confirm that the upgrade from  2.263.4 to  2.303.2 fixed the Global configuration save/apply binding issues for us. ( i.e. - Global Security/Configure System/etc. ) Once we were able to generate a complete list of plugins that were unique only to the problematic Jenkins master, we installed those same plugins on a separate test Jenkins master and starting uninstalling/removing those specific plugins one by one. By completely removing all references of the coding-webhook plugin, we were able to successfully save/apply new binding changes to all Jenkins jobs again. I should note that the coding-webhook plugin was previously uninstalled during the earlier plugin troubleshooting efforts, but the plugin's homedir under ${JENKINS_HOME/plugins} was still present along with other recursive references to the plugin's .JPI file under ${JENKINS_HOME}. The strange part is that the actual .JPI file was completely removed during the initial plugin uninstall and wasn't found anywhere under the ${JENKINS_HOME} which was a red flag. Another giveaway for us was intermittent error messages about the coding-webhook plugin were observed from time-to-time while refreshing the installed plugins list in the Jenkins UI after a restart of Jenkins. It wasn't a continuous error message and would go away after a certain amount of time, but would show up at the bottom of page after restarting Jenkins and then immediately refreshing the installed plugins list afterwards. While removing all references of the coding-webhook plugin resolved the save/apply Jenkins jobs issue, we had to wait until upgrading to version 2.303.2 to officially confirm that the global save/apply binding issues that we encountered had been resolved for us. Thank you Mark Waite and everyone else that took the time to reply for helping to guide us with the direction on troubleshooting, diagnosing and ultimately getting us past these issues!
            Hide
            markewaite Mark Waite added a comment -

            I'm glad to hear it. The coding webhook plugin has been deprecated in favor of the coding.net Jenkins integration. Since that site is in a language I do not read, I assume that it describes something about Jenkins and their integration with Jenkins.

            Show
            markewaite Mark Waite added a comment - I'm glad to hear it. The coding webhook plugin has been deprecated in favor of the coding.net Jenkins integration . Since that site is in a language I do not read, I assume that it describes something about Jenkins and their integration with Jenkins.
            Hide
            markewaite Mark Waite added a comment -

            Closing as "won't fix" because the coding-webhook plugin is deprecated.

            Show
            markewaite Mark Waite added a comment - Closing as "won't fix" because the coding-webhook plugin is deprecated.
            Hide
            alexanderstohr Alexander Stohr added a comment -

            this problem might be similar to this one dealing with vsphere plugin:
            https://issues.jenkins.io/browse/JENKINS-67234

            Show
            alexanderstohr Alexander Stohr added a comment - this problem might be similar to this one dealing with vsphere plugin: https://issues.jenkins.io/browse/JENKINS-67234

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              clsmith4 Charles Smith
              Votes:
              32 Vote for this issue
              Watchers:
              46 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: