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

Layout issues on build summary page from Jenkins LTS 1.625.2

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Critical Critical
    • core
    • Jenkins ver. 1.625.2,1.625.3
      SLOC count plugin, Chrome 47, IE 11

      We are planning to shift to the latest LTS release version 1.625.2 or 1.625.3 but we are facing layout issues on build summary page which is displayed by clicking the individual build number link.
      We have some information that is displayed from internal plugin development team along with information displayed in tabular form from SLOCCount plugin, PTC Integrity on this page after build completion.

      Currently we use Jenkins v1.580.3 which displays all information correctly but the latest LTS version has serious layout issues due to which we are unable to see the entire data that is required to be displayed.

      From attachment 1 you can see that the 1st table on the page is in correct alignment as it is a part of the <div class=main-panel> tag in layout but, 2nd table onwards the data shifts to left corner of page as it moves out of the <div class=main-panel> tag. All the data that we wish to display should be a part of the main-panel as we have defined to be in that way in our jelly scripts but the <div> closes after adding just a single row in the main-panel causing loss of data.

      Attachment 2 shows the correct format as coming from older version 1.580.3

        1. Build_Summary_Layout_Prob.png
          58 kB
          Anusha Bilgi
        2. Correct_layout_build_summary.png
          43 kB
          Anusha Bilgi
        3. Snapshot1.png
          97 kB
          Anusha Bilgi
        4. Snapshot2.png
          89 kB
          Anusha Bilgi

            Unassigned Unassigned
            anushabilgi Anusha Bilgi
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: