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

Build display names wrapped and/or truncated in build history when build is running

    XMLWordPrintable

    Details

    • Similar Issues:
    • Released As:
      Jenkins 2.239

      Description

      I think this is only happening since Jenkins core 2.238 and thus I extremely naively suspect an unfortunate side effect from JENKINS-61973 (Félix Queiruga Balado), but of course I might be wrong...

      See screenshot: Actually the layout jumps – initially the build display names are shown full, and then (via JS?) the first one is wrapped, while all the others are just truncated:

      Oops , when no build is running for the pipeline job, then it looks OK: Unable to embed resource: image-2020-05-29-09-48-48-840.png of type image/png

      If there are less stages in a pipeline the build display names are shown in full the whole time, but the one for the currently running build is wrapped:

        Attachments

          Activity

          Hide
          fqueiruga Félix Queiruga Balado added a comment - - edited

          There are 2 different things going on here

          That PR changed the page layout to flexbox, it's happening ever since. The shrinking side panel can be fixed by setting flex-shrink: 0 on CSS for desktop screens on the #side-panel (see the layout-commons.css file). You are welcome to provide a PR fixing this

          When the build names are longer than (I think) 70-80% width of the build history list, they break into the next line. I did not touch the line break strategy. In fact, it's something that has been going on for a while and I don't think it can be fixed any time soon.

          Show
          fqueiruga Félix Queiruga Balado added a comment - - edited There are 2 different things going on here That PR changed the page layout to flexbox, it's happening ever since. The shrinking side panel can be fixed by setting flex-shrink: 0  on CSS for desktop screens on the #side-panel (see the layout-commons.css file). You are welcome to provide a PR fixing this When the build names are longer than (I think) 70-80% width of the build history list, they break into the next line. I did not touch the line break strategy. In fact, it's something that has been going on for a while and I don't think it can be fixed any time soon.
          Hide
          reinholdfuereder Reinhold Füreder added a comment -

          Félix Queiruga Balado Thanks for your quick update/comment: frankly, I am not a web developer and rather less than more following your explanation...
          => Actually the first thing – the one that can be fixed according to you – is by far the most important one for me and also sufficient!
          => Thus I would be very, very grateful, if you (due to obviously being an expert in this area) could do/fix "only" that... THANKS!

          Show
          reinholdfuereder Reinhold Füreder added a comment - Félix Queiruga Balado Thanks for your quick update/comment: frankly, I am not a web developer and rather less than more following your explanation... => Actually the first thing – the one that can be fixed according to you – is by far the most important one for me and also sufficient! => Thus I would be very, very grateful, if you (due to obviously being an expert in this area) could do/fix "only" that... THANKS!
          Hide
          fqueiruga Félix Queiruga Balado added a comment -

          Will do

          Show
          fqueiruga Félix Queiruga Balado added a comment - Will do
          Hide
          fqueiruga Félix Queiruga Balado added a comment -

          Created a PR here: https://github.com/jenkinsci/jenkins/pull/4755

          Can you try it out?

          Show
          fqueiruga Félix Queiruga Balado added a comment - Created a PR here: https://github.com/jenkinsci/jenkins/pull/4755 Can you try it out?
          Hide
          reinholdfuereder Reinhold Füreder added a comment -

          Félix Queiruga Balado Thanks!
          Ad "Can you try it out?": Frankly, I am not sure how, and thus trust you as well as https://github.com/jenkinsci/jenkins/pull/4755#pullrequestreview-421468698

          Show
          reinholdfuereder Reinhold Füreder added a comment - Félix Queiruga Balado Thanks! Ad " Can you try it out? ": Frankly, I am not sure how, and thus trust you as well as https://github.com/jenkinsci/jenkins/pull/4755#pullrequestreview-421468698
          Show
          danielbeck Daniel Beck added a comment - Frankly, I am not sure how https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/main/jenkins-war/2.239-rc29993.4fb39f1f9a47/
          Hide
          reinholdfuereder Reinhold Füreder added a comment -

          Thanks for fix and release: it looks good (in 2.239)
          (Hm, I am confused why I have not received a notification email for e.g. Daniel's comment https://issues.jenkins-ci.org/browse/JENKINS-62506?focusedCommentId=391714&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-391714!? I think I might need to contact our system admins)

          Show
          reinholdfuereder Reinhold Füreder added a comment - Thanks for fix and release: it looks good (in 2.239) (Hm, I am confused why I have not received a notification email for e.g. Daniel's comment https://issues.jenkins-ci.org/browse/JENKINS-62506?focusedCommentId=391714&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-391714!? I think I might need to contact our system admins)
          Hide
          danielbeck Daniel Beck added a comment -

          Sent me to the spam folder once too often?

          Show
          danielbeck Daniel Beck added a comment - Sent me to the spam folder once too often?

            People

            Assignee:
            fqueiruga Félix Queiruga Balado
            Reporter:
            reinholdfuereder Reinhold Füreder
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: