You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[JENKINS-24687] Broken job list if build name is extended #23443
Alright. So this isn't related to anything I changed and I don't have time to "fix" it and I can't justify to my work that I should find time. That said, I did take a peek at it.
For anyone who wants to look at it, something like the following could work.
But it has side effects and potential side effects:
It shrinks the progress bar in some cases
You cannot read the entire name because it is no longer wrapped and shows ellipses
The part you can read is the least significant part (like the year). (May be fixable with more CSS but that may look weird, so you could add more markup and even more css to try and compensate)
On the job page, you really only have 9 characters of space to work with (ellipses take up two of those)
Someone else can consider these issues. I don't agree with making the build name long. Please don't reassign to me.
Alright. So this isn't related to anything I changed and I don't have time to "fix" it and I can't justify to my work that I should find time. That said, I did take a peek at it.
For anyone who wants to look at it, something like the following could work.
But it has side effects and potential side effects:
It shrinks the progress bar in some cases
You cannot read the entire name because it is no longer wrapped and shows ellipses
The part you can read is the least significant part (like the year). (May be fixable with more CSS but that may look weird, so you could add more markup and even more css to try and compensate)
On the job page, you really only have 9 characters of space to work with (ellipses take up two of those)
Someone else can consider these issues. I don't agree with making the build name long. Please don't reassign to me.
Activity
jenkins-infra-bot commentedon Sep 12, 2014
vikulin:
Raw content of original comment:
similar issue in an another section
jenkins-infra-bot commentedon Sep 12, 2014
Raw content of original comment:
Basically the same issue as
JENKINS-24589.jenkins-infra-bot commentedon May 15, 2015
vikulin:
Raw content of original comment:
This is not the same issue as
JENKINS-24589.Firstly: in my case is used Version Number Plugin
And the issue is still reproducing (jenkins 1.613)
See screenshot.
jenkins-infra-bot commentedon May 23, 2015
vikulin:
Raw content of original comment:
Reproduced on 1.614.
JENKINS-28425did not fix the issue.jenkins-infra-bot commentedon May 26, 2015
Raw content of original comment:
JENKINS-28425is actually in 1.615, the changelog is wrong.jenkins-infra-bot commentedon May 26, 2015
Raw content of original comment:
Fixed the changelog.
jenkins-infra-bot commentedon May 27, 2015
vikulin:
Raw content of original comment:
Reproduced on 1.615.
jenkins-infra-bot commentedon May 27, 2015
Raw content of original comment:
Alright. So this isn't related to anything I changed and I don't have time to "fix" it and I can't justify to my work that I should find time. That said, I did take a peek at it.
For anyone who wants to look at it, something like the following could work.
a.model-link.inside { text-overflow: ellipsis; width: 100%; white-space: nowrap; overflow: hidden; max-width: 100px; display: inline-block; }But it has side effects and potential side effects:
Someone else can consider these issues. I don't agree with making the build name long. Please don't reassign to me.
jenkins-infra-bot commentedon Nov 24, 2025
[Original
duplicatesfrom Jira: JENKINS-24589]jenkins-infra-bot commentedon Nov 24, 2025
[Original
relates_tofrom Jira: JENKINS-28425]jenkins-infra-bot commentedon Nov 24, 2025
[Original
relates_tofrom Jira: JENKINS-24688]