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

Configure UI broken by GitLab merge request plugin after upgrade to 2.277.1

      After I had upgraded to 2.277.1 the configure page UI seems to be broken. If I click on apply or save nothing happens. It gives no response. After some research I came to the suspicion that the SSH Credentials plugin is causing this bug. Hence after downgrading it to 1.18.0 from 1.18.1. The UI of the configure page was fixed. I will attach some images for reference. Kindly Deal with this as soon as possible. This is preventing me from configuring any projects.

          [JENKINS-65243] Configure UI broken by GitLab merge request plugin after upgrade to 2.277.1

          Jishwin created issue -
          Oleg Nenashev made changes -
          Assignee New: Matt Sicker [ jvz ]
          Matt Sicker made changes -
          Labels New: tables-to-divs-regression

          Matt Sicker added a comment -

          This is probably a tables-to-div migration issue. Thanks for the report!

          Matt Sicker added a comment - This is probably a tables-to-div migration issue. Thanks for the report!

          Mark Waite added a comment - - edited

          I can't duplicate the problem as described,. Can you provide more details so that others can duplicate the problem?

          As far as I can tell from the ssh-credentials plugin source code, there are no references to HTML tables in any of the UI components. I don't see how it could cause a regression in 2.277.1 job configuration. I confirmed that my freestyle and pipeline jobs that use ssh credentials can be saved with 2.277.1.

          If rollback to 1.18.0 resolved the issue, then it is not a tables to divs issue. 1.18 was released 15 months ago with no changes related to tables to divs. 1.18.1 was released 2 months ago and only changed test infrastructure, not code functionality.

          I think something else is the root cause of the failure to save that configuration. Could you assure that you've used the instructions in the Jenkins 2.277.1 upgrade guide and in the table to div layout migration to investigate the issue? If that does not bring you to a complete solution, then include the detailed information in this issue. That should include the precise list of plugins installed and the type of job that is failing to save.

          Mark Waite added a comment - - edited I can't duplicate the problem as described,. Can you provide more details so that others can duplicate the problem? As far as I can tell from the ssh-credentials plugin source code, there are no references to HTML tables in any of the UI components. I don't see how it could cause a regression in 2.277.1 job configuration. I confirmed that my freestyle and pipeline jobs that use ssh credentials can be saved with 2.277.1. If rollback to 1.18.0 resolved the issue, then it is not a tables to divs issue. 1.18 was released 15 months ago with no changes related to tables to divs. 1.18.1 was released 2 months ago and only changed test infrastructure, not code functionality. I think something else is the root cause of the failure to save that configuration. Could you assure that you've used the instructions in the Jenkins 2.277.1 upgrade guide and in the table to div layout migration to investigate the issue? If that does not bring you to a complete solution, then include the detailed information in this issue. That should include the precise list of plugins installed and the type of job that is failing to save.
          Mark Waite made changes -
          Component/s New: _unsorted [ 19622 ]
          Component/s Original: ssh-credentials-plugin [ 17424 ]

          Mark Waite added a comment -

          I reassigned this from ssh-credentials to _unsorted because the issue is not related to ssh-credentials plugin. Without more data from the user, we can't deduce where the issue is, but I'm confident that the issue is not in the ssh-credentials plugin.

          Mark Waite added a comment - I reassigned this from ssh-credentials to _unsorted because the issue is not related to ssh-credentials plugin. Without more data from the user, we can't deduce where the issue is, but I'm confident that the issue is not in the ssh-credentials plugin.
          Jishwin made changes -
          Attachment New: Screenshot from 2021-04-12 16-51-34.png [ 54458 ]
          Jishwin made changes -
          Comment [ Firstly, sorry for the late reply. Debugging on my own is not an option as it requires me to disable plugins which is going to create problems with production. I am attaching all the plugins that is currently installed. And I did follow the installation guide.  !Screenshot from 2021-04-12 16-51-34.png! ]
          Jishwin made changes -
          Attachment New: Screenshot from 2021-04-12 16-53-31.png [ 54459 ]

            Unassigned Unassigned
            jishwin12 Jishwin
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: