-
Bug
-
Resolution: Fixed
-
Major
-
Jenkins Core 2.238 -- the latest and greatest ;-)
-
-
Jenkins 2.239
I think this is only happening since Jenkins core 2.238 and thus I extremely naively suspect an unfortunate side effect from JENKINS-61973 (fqueiruga), 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: 
[JENKINS-62506] Build display names wrapped and/or truncated in build history when build is running
Reinhold Füreder
created issue -
Reinhold Füreder
made changes -
| Attachment | New: screenshot-1.png [ 51349 ] |
Reinhold Füreder
made changes -
| Description |
Original:
I think this is only happening since Jenkins core 2.238 and thus I extremely naively suspect an unfortunate side effect from 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: !image-2020-05-29-09-47-16-772.png|thumbnail! Oops (!), when no build is running for the pipeline job, then it looks OK: !image-2020-05-29-09-48-48-840.png|thumbnail! 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: !image-2020-05-29-09-51-08-944.png|thumbnail! |
New:
I think this is only happening since Jenkins core 2.238 and thus I extremely naively suspect an unfortunate side effect from 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: !image-2020-05-29-09-47-16-772.png|thumbnail! Oops (!), when no build is running for the pipeline job, then it looks OK: !screenshot-1.png|thumbnail! 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: !image-2020-05-29-09-51-08-944.png|thumbnail! |
Reinhold Füreder
made changes -
| Description |
Original:
I think this is only happening since Jenkins core 2.238 and thus I extremely naively suspect an unfortunate side effect from 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: !image-2020-05-29-09-47-16-772.png|thumbnail! Oops (!), when no build is running for the pipeline job, then it looks OK: !screenshot-1.png|thumbnail! 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: !image-2020-05-29-09-51-08-944.png|thumbnail! |
New:
I think this is only happening since Jenkins core 2.238 and thus I extremely naively suspect an unfortunate side effect from 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: !image-2020-05-29-09-47-16-772.png|thumbnail! Oops (!), when no build is running for the pipeline job, then it looks OK: !image-2020-05-29-09-48-48-840.png|thumbnail! 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: !image-2020-05-29-09-51-08-944.png|thumbnail! |
Reinhold Füreder
made changes -
| Attachment | Original: screenshot-1.png [ 51349 ] |
Reinhold Füreder
added a comment - fqueiruga 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!
Reinhold Füreder
added a comment - fqueiruga 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! 
| Assignee | New: Félix Queiruga Balado [ fqueiruga ] |
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
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.