After we upgraded to 2.426.3 the inside of all jobs configuration was a mess.

      All the parameters and options were unnested, thus, when modifying and saving an existing job, new options/parameters were added to the config.

          [JENKINS-72639] Job configuration has all options unnested

          Mark Waite added a comment -

          I'm not able to duplicate the problem as described. "How to report an issue" provides guidance on the type of information that is needed so that others can duplicate the problem.

          It is possible that one or more of the plugin versions installed on your controller needs to be updated. If you haven't updated to the most recent releases of all the plugins you are using, that is a good first step.

          If the problem persists after updating all the plugins to their most recent releases, refer to configuration form modernization diagnosis steps for more ideas of things that you can check.

          Mark Waite added a comment - I'm not able to duplicate the problem as described. "How to report an issue" provides guidance on the type of information that is needed so that others can duplicate the problem. It is possible that one or more of the plugin versions installed on your controller needs to be updated. If you haven't updated to the most recent releases of all the plugins you are using, that is a good first step. If the problem persists after updating all the plugins to their most recent releases, refer to configuration form modernization diagnosis steps for more ideas of things that you can check.

          Jaakko added a comment - - edited

          UPDATE: After updating all remaining plugins the issue seems to be fixed.
          Keeping explanation of issue below.

          I think I see same kind of UI behaviour as Bob mentioned. 

          What I did

          • Backup version: Jenkins LTS 2.401.1
          • Installed Jenkins LTS 2.426.3 on a different host
          • Applied the backup of Jenkins LTS 2.401.1

          My backup consisted of

          • all jobs (excluding builds dir for each job)
          • Exlude following dirs: war, cache, tools, workspace

          In my case the job configurations look unchanged, but sections which should be collapsed are expanded. The attached screenshot offers better explanation I hope.

          Jaakko added a comment - - edited UPDATE: After updating all remaining plugins the issue seems to be fixed. Keeping explanation of issue below. I think I see same kind of UI behaviour as Bob mentioned.  What I did Backup version: Jenkins LTS 2.401.1 Installed Jenkins LTS 2.426.3 on a different host Applied the backup of Jenkins LTS 2.401.1 My backup consisted of all jobs (excluding builds dir for each job) Exlude following dirs: war, cache, tools, workspace In my case the job configurations look unchanged, but sections which should be collapsed are expanded. The attached screenshot offers better explanation I hope.

          Mark Waite added a comment -

          Thanks jamov. I still can't duplicate the issue and there is not enough information for others to duplicate the issue, but a plugin upgrade resolved the issue for you. I'm closing this as "Won't fix" because I don't plan to spend more time investigating it unless more details are provided that others can use to duplicate the problem in their environment. Those details would need to include the Jenkins version before the upgrade and the list of plugins and their versions. It would need to include the list of plugins and their versions after the upgrade. It would need to include a sample job definition that shows the issue.

          Mark Waite added a comment - Thanks jamov . I still can't duplicate the issue and there is not enough information for others to duplicate the issue, but a plugin upgrade resolved the issue for you. I'm closing this as "Won't fix" because I don't plan to spend more time investigating it unless more details are provided that others can use to duplicate the problem in their environment. Those details would need to include the Jenkins version before the upgrade and the list of plugins and their versions. It would need to include the list of plugins and their versions after the upgrade. It would need to include a sample job definition that shows the issue.

          Andrew Adkins added a comment -

          For anyone else who might be experiencing this issue we resolved it on our instance by upgrading from build-timeout:1.20 to 1.32

          Andrew Adkins added a comment - For anyone else who might be experiencing this issue we resolved it on our instance by upgrading from build-timeout:1.20 to 1.32

          Dan Wang added a comment - - edited

          aadkins 

          Thanks a lot for your advice, this save my life. "upgrading from build-timeout:1.20 to 1.32" can resolve this issue.

          Dan Wang added a comment - - edited aadkins   Thanks a lot for your advice, this save my life. "upgrading from build-timeout:1.20 to 1.32" can resolve this issue.

            Unassigned Unassigned
            bogdan_condur Bob
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: