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

Configure UI completely broken after upgrade to 2.264

      Report all issues with a complete plugin list, and a screenshot

      JENKINS_HOST=username:password@myhost.com:port
      curl -sSL "http://$JENKINS_HOST/pluginManager/api/xml?depth=1&xpath=/*/*/shortName|/*/*/version&wrapper=plugins" | perl -pe 's/.*?<shortName>([\w-]+).*?<version>([^<]+)()(<\/\w+>)+/\1 \2\n/g'|sed 's/ /:/'
       

      Check if your plugin already has an issue reported https://issues.jenkins.io/secure/Dashboard.jspa?selectPageId=20741 artifactory is https://github.com/jfrog/jenkins-artifactory-plugin/issues/350

      If you know which plugin is causing the issue report a new issue, including steps to reproduce and screenshots and label it with 'tables-to-divs-regression'

      How to identify which plugin is causing the issue

      1. check plugins list against open issues on https://issues.jenkins.io/secure/Dashboard.jspa?selectPageId=20741
      2. then if no open issue matches:

      • disable plugins in groups of about 10 and record which ones you disabled
      • Restart Jenkins
      • If you can still reproduce keep disabling
      • Once you can't reproduce enable plugins one by one until you find which one it is
      • Then report an issue with the label 'tables-to-divs-regression'

      How to triage someone else's issue

      1. check plugins list against open issues on https://issues.jenkins.io/secure/Dashboard.jspa?selectPageId=20741
      2. then if no open issue matches:

      curl https://issues.jenkins.io/secure/attachment/53350/53350_jenkins-basith-16112020.txt | sort > abdul-bas-plugins.txt
      cat abdul-bas-plugins.txt | cut -d ':' -f 1 | sort > plugins.filtered.txt # remove versions as CLI complains when old versions are there
      wget https://github.com/jenkinsci/plugin-installation-manager-tool/releases/download/2.1.2/jenkins-plugin-manager-2.1.2.jar
      wget https://get.jenkins.io/war/2.266/jenkins.war
      export JENKINS_HOME=~/.jenkins-64072
      java -jar jenkins-plugin-manager-2.1.2.jar -f abdul-bas-plugins.txt -d ~/.jenkins-64072/plugins --war jenkins.war
      java -jar jenkins.war
      
      • Normally create a new freestyle job and then reproduce the issue, (requires enough information with steps to reproduce, sometimes it is a different page or requires specific config)
      • Once reproduced disable plugins in groups of about 10 and record which ones you disabled
      • Restart Jenkins
      • If you can still reproduce keep disabling
      • Once you can't reproduce enable plugins one by one until you find which one it is
      • Then report an issue with the label 'tables-to-divs-regression'

      original text

      After upgrade to 2.264.1 via yum package, the confgure UI of all my projects was borked, showing things that the project didn't support, preventing modification and updates to jobs.  Jobs were still running correctly however.  Looking at JavaScript console there were alot of errors in js files.  console log attached.  

       

      Fixed by downgrading to 2.263.1 via yum downgrade and temporarily locking the version.  While the UI appears better in 2.263.1, some boxes are still long and an error is still received in the console:

       

      hudson-behavior.js:2982 Uncaught SyntaxError: Unexpected token ')'
       at onSuccess (combobox.js:19)
       at klass.respondToReadyState (prototype.js:1657)
       at klass.onStateChange (prototype.js:1600)
       at XMLHttpRequest.<anonymous> (prototype.js:414)
      

       

        1. 1.txt
          3 kB
        2. atlas-1603912761063.log
          22 kB
        3. branch-api.png
          branch-api.png
          14 kB
        4. configureClouds.png
          configureClouds.png
          292 kB
        5. ConfigureUIBroken_PublishOverFTP.png
          ConfigureUIBroken_PublishOverFTP.png
          305 kB
        6. finland-image1.PNG
          finland-image1.PNG
          29 kB
        7. image-2020-10-30-15-25-56-938.png
          image-2020-10-30-15-25-56-938.png
          118 kB
        8. image-2020-10-30-15-27-16-916.png
          image-2020-10-30-15-27-16-916.png
          118 kB
        9. image-2020-11-03-21-10-10-643.png
          image-2020-11-03-21-10-10-643.png
          33 kB
        10. image-2020-11-06-09-45-42-994.png
          image-2020-11-06-09-45-42-994.png
          35 kB
        11. image-2020-11-10-19-10-02-083.png
          image-2020-11-10-19-10-02-083.png
          68 kB
        12. image-2020-11-11-09-47-08-180.png
          image-2020-11-11-09-47-08-180.png
          48 kB
        13. image-2020-11-18-09-05-02-548.png
          image-2020-11-18-09-05-02-548.png
          37 kB
        14. image-2020-11-18-09-06-44-059.png
          image-2020-11-18-09-06-44-059.png
          51 kB
        15. image-2020-11-18-09-07-49-596.png
          image-2020-11-18-09-07-49-596.png
          47 kB
        16. image-2020-11-18-10-40-53-012.png
          image-2020-11-18-10-40-53-012.png
          78 kB
        17. image-2020-11-18-10-41-57-764.png
          image-2020-11-18-10-41-57-764.png
          7 kB
        18. image-2020-11-18-10-44-20-271.png
          image-2020-11-18-10-44-20-271.png
          79 kB
        19. image-2020-11-23-22-53-45-011.png
          image-2020-11-23-22-53-45-011.png
          246 kB
        20. image-2020-11-23-23-03-02-021.png
          image-2020-11-23-23-03-02-021.png
          208 kB
        21. image-2021-01-14-13-49-48-253.png
          image-2021-01-14-13-49-48-253.png
          158 kB
        22. image-2021-01-30-03-13-41-175.png
          image-2021-01-30-03-13-41-175.png
          92 kB
        23. image-2021-01-30-03-15-12-305.png
          image-2021-01-30-03-15-12-305.png
          47 kB
        24. image-2021-01-30-03-21-29-377.png
          image-2021-01-30-03-21-29-377.png
          92 kB
        25. image-2021-01-30-03-21-51-931.png
          image-2021-01-30-03-21-51-931.png
          174 kB
        26. issues.png
          issues.png
          60 kB
        27. jenkins_2.263.1-not-so-bad-ui.jpg
          jenkins_2.263.1-not-so-bad-ui.jpg
          76 kB
        28. jenkins_2.264.1-borked-ui.jpg
          jenkins_2.264.1-borked-ui.jpg
          99 kB
        29. jenkins_plugins_installed.docx
          21 kB
        30. jenkins_plugins_list
          15 kB
        31. jenkins_plugins.txt
          3 kB
        32. jenkins_plugins.xml
          10 kB
        33. jenkins-basith-11112020.txt
          6 kB
        34. jenkins-basith-16112020.txt
          6 kB
        35. jenkins-plugins-installed
          9 kB
        36. jenkins plugins in use.txt
          19 kB
        37. jenkins plugins in use - correct format.txt
          9 kB
        38. jsErrors.png
          jsErrors.png
          97 kB
        39. laksh - jenkins plugins.txt
          6 kB
        40. plugin.txt
          7 kB
        41. plugins.rossc.txt
          6 kB
        42. plugins.rossc-2.txt
          3 kB
        43. plugins.txt
          5 kB
        44. plugins.txt
          2 kB
        45. Plugins.txt
          4 kB
        46. plugins-1.txt
          7 kB
        47. plugins-18-11.txt
          7 kB
        48. plugins-2.txt
          3 kB
        49. Project1.png
          Project1.png
          1.22 MB
        50. Project2.png
          Project2.png
          1.01 MB
        51. Screenshot 2020-10-29 170505.png
          Screenshot 2020-10-29 170505.png
          53 kB
        52. Screenshot 2020-10-29 170642.png
          Screenshot 2020-10-29 170642.png
          84 kB
        53. Screenshot 2020-11-18 at 10.24.57 AM.png
          Screenshot 2020-11-18 at 10.24.57 AM.png
          63 kB
        54. Screenshot 2020-11-18 at 10.26.22 AM.png
          Screenshot 2020-11-18 at 10.26.22 AM.png
          57 kB
        55. Screenshot 2020-11-18 at 10.27.20 AM.png
          Screenshot 2020-11-18 at 10.27.20 AM.png
          70 kB
        56. Screenshot 2022-01-02 at 18.48.38.png
          Screenshot 2022-01-02 at 18.48.38.png
          221 kB
        57. Screenshot from 2020-11-23 23-02-24.png
          Screenshot from 2020-11-23 23-02-24.png
          224 kB

          [JENKINS-64072] Configure UI completely broken after upgrade to 2.264

          Atul added a comment -

          Thanks a ton markewaite for looking into this. Will upgrade all the plugins as mentioned as will share the results.

          Atul added a comment - Thanks a ton markewaite  for looking into this. Will upgrade all the plugins as mentioned as will share the results.

          kunal Jha added a comment -

          In our case we were able to narrow down the problem by applying the binary sort of disabling the plugins. 

          In our test environment of jenkins 

          i followed this approach. 

          // code placeholder
          
          cd $JENKINS_HOME/plugins/
          // step 1
          ls *.jpi|sort |egrep -v "workflow|pipeline|aws|cas-plugin"|grep -i  "^[a-j]"|while read line ; do  touch ${line}.disabled ; done
          systemctl restart jenkins
          
          // problem exists when opening the jenkins configure system end point.
          // https://${jenkins-url}/configure and got error like below.
          rm -rf [a-j]*.disabled
          
          // step 2
          ls *.jpi|sort |egrep -v "workflow|pipeline|aws|cas-plugin"|grep -i "^[f-j]"|while read line ; do touch ${line}.disabled ; done
          systemctl restart jenkins
          
          // problem exists when opening the jenkins configure system end point.
          // https://${jenkins-url}/configure and got error like below.
          rm -rf [f-j]*.disabled
          
          // step 3
          ls *.jpi|sort |egrep -v "workflow|pipeline|aws|cas-plugin"|grep -i "^[h-j]"|while read line ; do touch ${line}.disabled ; done 
          systemctl restart jenkins 
          // problem exists when opening the jenkins configure system end point. 
          // https://${jenkins-url}/configure and got error like below.
          rm -rf [f-j]*.disabled
          
          // step 4 
          ls *.jpi|sort |egrep -v "workflow|pipeline|aws|cas-plugin"|grep -i "^j"|while read line ; do touch ${line}.disabled ; done 
          systemctl restart jenkins 
          // problem exists when opening the jenkins configure system end point. 
          // https://${jenkins-url}/configure and got error like below.
          
          
          and finally i was able to identify when i disabled javadoc.jpi.disabled i was able to load the page normally.

           

           

           

           

          and finally i was able to narrow down the plugin causing the issue for me when i disabled the plugin javadoc.    i was able to save the options in Jenkins > Configure System without any problem.  

          kunal Jha added a comment - In our case we were able to narrow down the problem by applying the binary sort of disabling the plugins.  In our test environment of jenkins  i followed this approach.  // code placeholder cd $JENKINS_HOME/plugins/ // step 1 ls *.jpi|sort |egrep -v "workflow|pipeline|aws|cas-plugin" |grep -i "^[a-j]" | while read line ; do touch ${line}.disabled ; done systemctl restart jenkins // problem exists when opening the jenkins configure system end point. // https://${jenkins-url}/configure and got error like below. rm -rf [a-j]*.disabled // step 2 ls *.jpi|sort |egrep -v "workflow|pipeline|aws|cas-plugin" |grep -i "^[f-j]" | while read line ; do touch ${line}.disabled ; done systemctl restart jenkins // problem exists when opening the jenkins configure system end point. // https://${jenkins-url}/configure and got error like below. rm -rf [f-j]*.disabled // step 3 ls *.jpi|sort |egrep -v "workflow|pipeline|aws|cas-plugin" |grep -i "^[h-j]" | while read line ; do touch ${line}.disabled ; done systemctl restart jenkins // problem exists when opening the jenkins configure system end point. // https://${jenkins-url}/configure and got error like below. rm -rf [f-j]*.disabled // step 4 ls *.jpi|sort |egrep -v "workflow|pipeline|aws|cas-plugin" |grep -i "^j" | while read line ; do touch ${line}.disabled ; done systemctl restart jenkins // problem exists when opening the jenkins configure system end point. // https://${jenkins-url}/configure and got error like below. and finally i was able to identify when i disabled javadoc.jpi.disabled i was able to load the page normally.         and finally i was able to narrow down the plugin causing the issue for me when i disabled the plugin  javadoc.     i was able to save the options in Jenkins > Configure System without any problem.  

          Mark Waite added a comment -

          kunaljha5 I'm not aware of any issue in the javadoc plugin related to tables to divs.

          Did you follow the instructions in the 2.277.1 upgrade guide and upgrade your plugins to the latest versions? If you did and that still shows an issue in the javadoc plugin, please submit a separate issue for the javadoc plugin. Include precise details of the plugin versions installed on your system and the detailed steps you perform in order to see the problem.

          Mark Waite added a comment - kunaljha5 I'm not aware of any issue in the javadoc plugin related to tables to divs. Did you follow the instructions in the 2.277.1 upgrade guide and upgrade your plugins to the latest versions? If you did and that still shows an issue in the javadoc plugin, please submit a separate issue for the javadoc plugin. Include precise details of the plugin versions installed on your system and the detailed steps you perform in order to see the problem.

          rajiv chirania added a comment - - edited

          Hi,

           

          Recently i upgraded the jenkins to 2.319.1

          After the upgrade whenever i go to any existing project to make some changes or ever for newly created project the save and apply is looking weird behind as shown in the picture.

          I have also uploaded the list of plugins i am using.

          Right now all the plugins are updated and no deprecated plugins are used.

          I also tried and confirmed not using any of the affected plugins are discussed in this ticket.

           

          jenkins_plugins_list

           

          Any help will be appreciated..

          rajiv chirania added a comment - - edited Hi,   Recently i upgraded the jenkins to 2.319.1 After the upgrade whenever i go to any existing project to make some changes or ever for newly created project the save and apply is looking weird behind as shown in the picture. I have also uploaded the list of plugins i am using. Right now all the plugins are updated and no deprecated plugins are used. I also tried and confirmed not using any of the affected plugins are discussed in this ticket.   jenkins_plugins_list   Any help will be appreciated..

          Mark Waite added a comment - - edited

          rajivchirania the list that you uploaded includes the following plugins that are known to have issues with configuration form modernization:

          • ivy - JENKINS-67449 - remove the ivy plugin and call ivy from a bat, powershell, or sh script

          The list of plugins you have includes deprecated plugins:

          • Multiple SCMs - remove the multiple SCMs plugin and use Jenkins Pipeline instead
          • Azure Commons plugin - upgrade to latest Azure AD plugin in hopes of being able to remove this plugin

          The list of plugins you have includes the following plugins with known security issues:

          • Mercurial plugin 2.10 - upgrade to 2.16 or remove the plugin
          • Azure AD plugin 1.2.0 - upgrade to at least 1.2.3
          • Bitbucket approve plugin 1.0.3 - remove the plugin
          • Role based authorization strategy 2.16 - upgrade to most recent release

          Steps you should take:

          • Remove the deprecated plugins (multiple SCMs)
          • Remove the plugins that are known to not work with configuration forms modernization (Ivy)
          • Upgrade all the plugins as instructed in the 2.277.1 upgrade guide

          See the community.jenkins.io configuration form modernization summary for more details

          Mark Waite added a comment - - edited rajivchirania the list that you uploaded includes the following plugins that are known to have issues with configuration form modernization : ivy - JENKINS-67449 - remove the ivy plugin and call ivy from a bat, powershell, or sh script The list of plugins you have includes deprecated plugins: Multiple SCMs - remove the multiple SCMs plugin and use Jenkins Pipeline instead Azure Commons plugin - upgrade to latest Azure AD plugin in hopes of being able to remove this plugin The list of plugins you have includes the following plugins with known security issues: Mercurial plugin 2.10 - upgrade to 2.16 or remove the plugin Azure AD plugin 1.2.0 - upgrade to at least 1.2.3 Bitbucket approve plugin 1.0.3 - remove the plugin Role based authorization strategy 2.16 - upgrade to most recent release Steps you should take: Remove the deprecated plugins (multiple SCMs) Remove the plugins that are known to not work with configuration forms modernization (Ivy) Upgrade all the plugins as instructed in the 2.277.1 upgrade guide See the community.jenkins.io configuration form modernization summary for more details

          Arunan C added a comment -

          Can we add Rundeck plugin too to the broken plugins dashboard? https://issues.jenkins.io/browse/JENKINS-65664

          Arunan C added a comment - Can we add Rundeck plugin too to the broken plugins dashboard? https://issues.jenkins.io/browse/JENKINS-65664

          Mark Waite added a comment -

          arunan done. I added the 'tables-to-divs-regression' label to that issue so that it is now visible in the list

          Mark Waite added a comment - arunan done. I added the 'tables-to-divs-regression' label to that issue so that it is now visible in the list

          Tim Jacomb added a comment -

          Closing given no updates in 6 months

          Tim Jacomb added a comment - Closing given no updates in 6 months

          Suresh Dega added a comment -

          Hi,

          Is this issue is resolved..? Because i also facing same issue in Jenkins 2.346.2 version, When i click Save and Apply button in ManageJenkins—>Manage and AssignRoles—>Save and Apply i'm getting "HTTP 403 No valid crumb was included in the request". Please help on this issue to fix.

          Suresh Dega added a comment - Hi, Is this issue is resolved..? Because i also facing same issue in Jenkins 2.346.2 version, When i click Save and Apply button in ManageJenkins—>Manage and AssignRoles—>Save and Apply i'm getting "HTTP 403 No valid crumb was included in the request". Please help on this issue to fix.

          Mark Waite added a comment -

          degasuresh asking for help in a closed issue is much less likely to actually get help than if you ask in one of the locations that handle questions. Especially asking a question related to a different symptom than the specific issue where you are making your comment.

          This issue is related to the transition of page layout from HTML table tags to HTML div tags. The issue you're describing is most likely not related to the page layout transition. However, in order to assure that the issue you are seeing is not related to the page layout transition, please follow all the steps described in https://community.jenkins.io/t/migrating-jenkins/894/5 . If you follow all those steps and still see the issue, you will increase the chances that others will be able to help you. You will also increase the chances that you'll solve the problem yourself.

          Mark Waite added a comment - degasuresh asking for help in a closed issue is much less likely to actually get help than if you ask in one of the locations that handle questions. Especially asking a question related to a different symptom than the specific issue where you are making your comment. This issue is related to the transition of page layout from HTML table tags to HTML div tags. The issue you're describing is most likely not related to the page layout transition. However, in order to assure that the issue you are seeing is not related to the page layout transition, please follow all the steps described in https://community.jenkins.io/t/migrating-jenkins/894/5 . If you follow all those steps and still see the issue, you will increase the chances that others will be able to help you. You will also increase the chances that you'll solve the problem yourself.

            Unassigned Unassigned
            jonl_percsol Jonathon Lamon
            Votes:
            48 Vote for this issue
            Watchers:
            77 Start watching this issue

              Created:
              Updated:
              Resolved: